> Hi,
>
> I am thinking about writing an app in C# 2.0 and starting to look into
> distribution strategies.
>
> Is it possible to distribute a setup program (VS, Installshield, Wise,
> etc.) which dynamically determines if the 2.0 runtime is installed, and
> if it is not it installs it from the internet from a resource made
> publicly available from Microsoft?
>
> I won't be happy if I have to incur the bandwidth cost of embedding the
> 2.0 redistributable files in my installation program. It would beg the
> question - does MS really think they can get away with shifting the
> burden of distributing their future on the backs of ISVs?
>
> If this is the case, any suggestions for small ISV's that cannot afford
> to distribute the runtime to interested users who may not even purchase
> the software?
>
> This is really a burden for shareware authors. It may force me to write
> the app in VB6.
>
> Thanks,
> Matthew

> Hello Matthew:
>
> Yes it is possible to detect and point your users to the correct .NET
> framework package for either VS 2003 (.NET 1.1 if you still need it )
> or VS 2005.
>
> No coding is needed if you use the VS "Setup and Deployment" 's Setup
> Project.
> The Setup Project project gives you much control over the installation
> details for commercial apps.   The Setup Wizard allows allows easier
> decision making but perhaps is a little less flexible with
> installation.
>
> Take a look at the potential of using the VS 2005 (or VS 2003) "Setup
> and Deployment" Project.   Specifically the VS 2003 Setup Project wil
> write a setup.ini
> for older products as InstallUrl",  to point to the MS deployment  for
> dotNET 1.1
>
> [MSILoader]
> MSIFileName=Your_Build_Here_Version123.msi
> [FXSection]
> SupportedRuntimes=1.1.4322
> InstallUrl=http://go.microsoft.com/fwlink/?LinkId=9832
> Message=1.1.4322
> UseDefaultMessage=1
>
> The VS 2005 Setup and Deployment Project will internally reference the
> same line:
> http://go.microsoft.com/fwlink/?LinkId=9832
> but will require the 2.0.50727 version for .NET 2.0 (for example).
>
> By the way, Setup Wizard will place the URL 'hook' inside the
> deployment project automagically.  Try deploying the project on a
> Windows XP box that does NOT have the .NET runtime installed.  You will
> see that that Setup Wizard will call out for the .NET deployment
> packages to the Web.
>
> Hope this helps.
>
> Matthew Copeland wrote:
> > Hi,
> >
> > I am thinking about writing an app in C# 2.0 and starting to look into
> > distribution strategies.
> >
> > Is it possible to distribute a setup program (VS, Installshield, Wise,
> > etc.) which dynamically determines if the 2.0 runtime is installed, and
> > if it is not it installs it from the internet from a resource made
> > publicly available from Microsoft?
> >
> > I won't be happy if I have to incur the bandwidth cost of embedding the
> > 2.0 redistributable files in my installation program. It would beg the
> > question - does MS really think they can get away with shifting the
> > burden of distributing their future on the backs of ISVs?
> >
> > If this is the case, any suggestions for small ISV's that cannot afford
> > to distribute the runtime to interested users who may not even purchase
> > the software?
> >
> > This is really a burden for shareware authors. It may force me to write
> > the app in VB6.
> >
> > Thanks,
> > Matthew