MSI Upgrade failure with WPS 4.61
I am creating an upgrade in WPS 4.61 for a package but when testing the MSI, it does not remove the old MSI.
I used the "Upgrades" and Added the old MSI file and it displayed the Upgrade Code etc as expected. After a Save, Complile then test, it does not uninstall the MSI which I added to the "Upgrades" in WPS.
I am not sure if this is relevant, but the MSI which we are upgrading, was upgraded from an older version of the application. ie. We are at the 2nd upgrade in the life of this application. All the versions of this application was installed by Windows Installer.
I used the "Upgrades" and Added the old MSI file and it displayed the Upgrade Code etc as expected. After a Save, Complile then test, it does not uninstall the MSI which I added to the "Upgrades" in WPS.
I am not sure if this is relevant, but the MSI which we are upgrading, was upgraded from an older version of the application. ie. We are at the 2nd upgrade in the life of this application. All the versions of this application was installed by Windows Installer.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
bkelly
19 years ago
Two ways to do an update with WPS:
1) Take your old MSI, and make any desired changes. Then in the General view, click the button to generate a new Product ID (must be unique). You'll get prompted to change the upgrade code or not as well- don't. The upgrade code for both your original and update package must match (in addition to being listed in the upgrade table).
2) I've not used it myself, but there is a tool called UpgradeSync provided in the suite that will take your new/upgrade MSI and ensure that the component GUIDs match up, etc. (which would not be a problem if you simply modified the original package).
All that said- make certian the Upgrade code in the property table matches for the two products (the new package upgrade code should be that of you old one).
1) Take your old MSI, and make any desired changes. Then in the General view, click the button to generate a new Product ID (must be unique). You'll get prompted to change the upgrade code or not as well- don't. The upgrade code for both your original and update package must match (in addition to being listed in the upgrade table).
2) I've not used it myself, but there is a tool called UpgradeSync provided in the suite that will take your new/upgrade MSI and ensure that the component GUIDs match up, etc. (which would not be a problem if you simply modified the original package).
All that said- make certian the Upgrade code in the property table matches for the two products (the new package upgrade code should be that of you old one).
Posted by:
pjohnson
19 years ago
Thanks for the comments.
It seemed to have been a versioning issue. To resolve the problem, I had to check the box 'Include maximum version in the range'.
By default it was left unchecked, which I guess explains why the 3rd upgrade did not upgrade the 2nd upgrade.
It seemed to have been a versioning issue. To resolve the problem, I had to check the box 'Include maximum version in the range'.
By default it was left unchecked, which I guess explains why the 3rd upgrade did not upgrade the 2nd upgrade.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.