J
JimC
Suppose a developer has a setup.exe file that can be downloaded
from his online site, rather than from a distribution CD.
If the targeted user were using a CD, of course it would be easy to
include dotnetfx.exe on the CD and install it silently (or relatively
silently) if needed.
But from an online download, how is the problem of getting .NET
Framework onto the target computer solved in a graceful manner?
That's a 25-MByte file, and while it is easy enough to make it
available to the targeted user from the developer's own site, this
entails an "untrivial" amount of bandwidth usage. Directing a user to the
Microsoft site with a large list of downloadable items confuses
the new user.
Am I missing something here? Does Microsoft place .NET
Framework by default?
from his online site, rather than from a distribution CD.
If the targeted user were using a CD, of course it would be easy to
include dotnetfx.exe on the CD and install it silently (or relatively
silently) if needed.
But from an online download, how is the problem of getting .NET
Framework onto the target computer solved in a graceful manner?
That's a 25-MByte file, and while it is easy enough to make it
available to the targeted user from the developer's own site, this
entails an "untrivial" amount of bandwidth usage. Directing a user to the
Microsoft site with a large list of downloadable items confuses
the new user.
Am I missing something here? Does Microsoft place .NET
Framework by default?