Last post Dec 30, 2008 05:45 AM by mudassarkhan
Dec 30, 2008 04:32 AM|Shaimaa Mohammad|LINK
I made a setup project and after building the setup there are 2 files:
Is there any way to gathering them into only one file ?
ApplicationName.msi can work without need of setup.exe existance
but setup.exe can't work without existing of ApplicationName.msi
Thank You in advance
Dec 30, 2008 05:42 AM|mudassarkhan|LINK
Ignore the setup.exe. The only file you need is Setup.msi which is ur main Setup File
Dec 30, 2008 05:45 AM|mudassarkhan|LINK
Also for ur Information
The Windows Installer package for the HelloWorld project. We can change its name to something more conventional by modifying the Output file name property in the setup project's Property Pages dialog.
The setup bootstrapper file, which reads
Setup.ini to determine the required installation tasks. This is the file that is run to start the installation.
Setup.exe will check for the required .NET runtime and prompt users to download it if it is not found on the target PC.
The initialization file used by Setup.exe to perform the required operations. In a simple setup project like this, Visual Studio .NET creates a reference to the MSI file containing the application's Windows Installer
package along with a reference to the required .NET Framework runtime. In more complex installations, it may contain other application-specific information.
To distribute an application, we usually should include all three of these files in our installation package. The user can run
Setup.exe, which checks whether the target machine has the correct version of the .NET Framework runtime installed. If not, it will prompt the user to download the runtime from Microsoft's website and install it. Once it is satisfied
that the required runtime is installed, it then invokes HelloWorld_Setup.msi to install the
If you are certain that your users will have the correct version of the CLR, such as in a controlled corporate environment, you can get away with distributing only the application installation
.msi file (such as HelloWorld_Setup.msi). In such case, you can change your setup project's
Bootstrapper property so that it does not create any bootstrapper files.