Hi,
So, if I do as you suggest and go to the upgrades page and add a new upgrade code by pointing it to my most recent Visual Studio based msi package (2.15) then will that goof up people who go to do a future upgrade who are already using one of the Advanced Installer versions?
If the upgrade code of the packages built with Advanced Installer for previous version is not the same with the one of the latest version created with Advanced Installer then you will have to add it to the list too.
I am assuming the upgrade code remained the same
If you changed only the ProductCode the UpgradeCode should be the same for all versions, so all of them should be automaticaly removed by the package you create with Advanced Installer and contains this UpgradeCode.
Regards,
Bogdan
FOLLOW US
Get the latest news in Application Packaging