We have an installer that we build with each release that allows for upgrades for every minor release, but when we do the yearly major release we would like to allow side-by-side installs. Note: both are registered to use the same file extension. To accomplish this, we change:
- the Product Name
- the Product Code GUID
- the Upgrade code GUID
- the GUID for 2 files in start menu shortcuts
This has given us the flexibility we need and works in almost every case. However, the file association is proving to be a bit of a handful.
Installing 17.x, then installing 18.x - everything works well. Both programs are registered to use the file extension properly, and both show up as separate entities in the "Open With" dialog. The default program for the file extension will even be 18.x. However, uninstalling 17.x removes the default registration along with the registration for 17.x.
Our current workaround is to ask the user to run the 18.x installer in repair mode and this usually fixes it, but it is not ideal. Does this sound like we have set up the file extension incorrectly in advanced installer, is this a limitation of the Windows file extension system, has this been fixed in a recent update of advanced installer I have not installed yet, or do you need more information?
Thank you in advance for your assistance,
-Mike