I have an Enterprise installer project (version 12.6.1) that is seemingly quite simple. It deploys the files for an ASP.NET application to a folder and then configures IIS. Two virtual directories are created: one for the application and another for some data (ie. simple virtual directory not configured as an application). The names of these virtual directories are set via properties that the user modifies in a custom dialog. The IIS settings do not have any install conditions attached, and we have an error policy to "Prompt user to skip item or rollback installation" if duplicate.
If we register the install with Windows Installer then this works flawlessly, but precludes the option of using the installer to deploy two copies [of the same version] of the application to the same server. The users typically desire multiple installations on the same server, so we have chosen not to register the install with Windows Installer. Upon making that change to our installation package (to not register with Windows Installer) the subsequent installations fail to configure IIS virtual directories, even though the properties have been modified during setup so that the names of the virtual directories are unique.
Am I missing something here? My expectation is that the installer will work the same way both times the package is installed, but there is definitely something different with the second install because the IIS configuration is never applied.
FOLLOW US
Get the latest news in Application Packaging