We have an ASP.NET 2.0 application available as a test download. Therefore, we do not control the environment in which it will be installed. Despite all our efforts to create a reliable installer, we still get a lot of messages about message problems.
We generate compiled .net files using a network deployment project. We then output the result and run it through the VS 2010 deployment project to create the MSI installer.
Here are some of the issues we face:
- It seems that the msi installer does not work with IIS7. In order for it to be installed correctly, compatibility with IIS6 must be installed, otherwise it will simply fail.
- Although the "RemovePreviousVersions" parameter is set to true, the installer almost never removes the unnecessary version and simply causes an error stating that the application is already installed.
We previously tried using the InnoSetup installer. It worked to a certain extent, but we had problems with the installed application connecting to the wrong application pool, and still did not find a way to determine the application pool through the InnoSetup script.
Can someone give me the final list of what you need to run the ASP.NET application on a computer running Windows XP or later with an unknown configuration? for example, install .NET 2.0, check box II6, copy files to x, create a virtual directory, etc.
Even better, does anyone know about the installer (or the InnoSetup extension) that does most of the configuration for you?
norgepaul
source share