I have a product that builds an EXE and also two MSI builds (for 32 and 64 bit).
Under Upgrades is set:
Automatically upgrade older product versions
Use Original Installation path when upgrading
Uninstall old version first
Supposing I install from the EXE. I then run the identical EXE again (no rebuild, no change of product code). I get the maintanance dialog "Modify Repair Remove" - which is correct.
However, any attempt to launch the matching MSI from the same build results in the dreaded MsgBox "Windows Installer: Another version of this product is already installed. Installation of this version cannot continue".
How does windows know the difference between the EXE and MSI from the same build?
( If I upgrade the product code and rebuild, the MSI does seem to replace the old EXE installation, at least.
And conversely, if i install from MSI, then run the EXE, it replaces the MSI installation regardless of whether I rebuild or change product code or not. )
Why the problem/confusion when both builds are the same going from .exe to MSI? Many thanks
The reason I ask is that my app is installed by either EXE or MSI, but internally downloads upgrade installers and executes them to update itself.
I am worried about losing the ability to control the installation using MSIs in Group Policy if the application has in the meantime upgraded itself by running a BootStrapped EXE.
FOLLOW US
Get the latest news in Application Packaging