Previously, I wrote a post about problems I was having creating a Minor Upgrade for a client. Here is the link to that post:
A reader left a comment and wanted to know what solution I found for this. Here’s the story.
If I write all the installers for a client, then creating Minor Upgrades doesn’t seem to be a problem, because I know what to do. But, if the client created the previous installers, and they want me to create a Minor Upgrade for them, I sometimes have problems because they are not versed in Best Practices. So, what do I do if I’m really stuck and just can’t get the Minor Upgrade to work?
I bend the rules a little. If I can’t get the Minor Upgrade to work, I’ll set it up so the Windows Installer thinks it’s a Major Upgrade, but I’ll increment the Product Version to be a number consistent with a Minor Upgrade. That way, the installer will uninstall the previous version before installing the new one. Here are the steps:
- Change the Windows Installer GUID codes in the manner you would for a Major Upgrade.
- Go to the Upgrades view and create the Major Upgrade item and indicate you want it to uninstall the previous version before installing the new one.
- Change the Product Version a small amount. For example, if the previous version is 1.5, then I might change it to be 1.6 or 1.5.5. Just sometime greater than the earlier version. I think to the Windows Installer, the new version number just has to be higher.
Now, I haven’t written about this before, because this is not really a Best Practice type of solution, and I really hope I don’t regret doing it. If you decide to use this method, please promise me you’ll test this exhaustingly before going live with your installation.