Creating a Setup file

Does anyone know how to create a setup package in .NET that will not only check for the .NET framework on the computer but if it doesn't find it, will automatically install it. I know how to get it to check for the framework and abort the installation, but I can't seem to figure out how to force it to automatically install the framework if it doesn't detect it. Is this possible?

I am not sure exactly how to do it... but its my understanding you wouldnt be able to include it with your installation...

Correct me if I am wrong but if its not installed, you will have to direct them to DL it from MS....

Anjari

You can include the framework with your distribution (on CD preferrably)...

As far as forcing the user install the copy of the framework that you would distribute with your application, I believe that would be unnecessary.

Is there after checking for the .NET framework to launch the bootstrap to install it from your .NET applications set up program? In other words, rather than just telling the user it needs to be installed to just install it?:confused:

The 'official' position is not to install it as part of your setup. The microsoft site states, yes check for it and then exit the setup with a message saying the Framework must be installed first. Yes I don't know why either.

Well, is there a way to manipulate the .NET Framework Bootstrap to only run IF it detects that it needs to?

Why does MS feel the need to make things so damn difficult!

Don't have the exact info to hand, however I know I have seen an example for DMAC which checks the registry entry for the version installed and feel sure research along those lines will yield results. I'm guessing but perhaps the reason for install it seperately is because a) the Framework is 23.1mb and b) by directing you to the site for installation you will always install the current version.

There is a bootstrap project going on at GotDotNet. I haven't actually tried this but I've heard good things:

http://www.gotdotnet.com/Community/W...a-d187d16f41f1

Very true, but a pain nonetheless (especially when end users aren't very computer literate) - but thank you for your assistance!

Cheers!