Hi all,

I'm a regular visitor to the site and have received many a helpful answer over the past couple of years, without actually needing to post myself, but despite several hours' searching I'm unable to find an answer to my specific situation - if there is one, I apologise. Hence this is my first post..

We have an in-house developed product which was packaged using Wise Package Studio by my predecessor. Since he left it has come to light that a particular component is being installed incorrectly. I've corrected this by opening his existing WSI project file and making the necessary changes, then rebuilding the MSI. The Product Version remains the same, as does the Upgrade Code, however Wise has given the package a new Product Code presumably due to the removal of a component and addition of a new one.

I have set up the Upgrade table with the following values;

Upgrade Code: (The upgrade code of both packages)
VersionMin: 8.5 (the version of both packages, new & old)
VersionMax: 8.5
Language: 1033
Attributes: <0x304> (Include min & max versions, ignore failure to remove)
Remove: <null>
ActionProperty: UPGRADE_1 (Which is in the SecureCustomProperties property)

My goal is to be able to roll out this new package to machines whether the existing package is present or not, however where present Windows Installer is insisting that a newer version is already installed, despite setting up the Upgrade table to include this product version.

I'm obviously doing something wrong, however I can't figure out what it is. I've tried many permutations of Upgrade attributes to no avail. Any help / advice would be greatly appreciated.

Thanks in advance.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2
HI Valiante ,

If you are doing a major upgrade then change the Product version too.

If you wanted to go with the same version of the application then you can use vbscript to uninstall the previous version and install the current one.
Answered 11/13/2011 by: mahendraKumar
Senior Yellow Belt

Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
to enforce a major upgrade you need to use a different product code and a different version,
the last portion of the version is ignored. e.g. 1.0.0.1 to 1.0.0.2 doesnt work, at least you need to increment one of the first three numbers (like 1.0.1.0).

in your case you could try to use 8.5.1 since 8.6 could cause confusion or problems once the vendor releases the "real" 8.6
Answered 11/14/2011 by: weberik
Yellow Belt

Please log in to comment
0
ORIGINAL: mahendraKumar
If you wanted to go with the same version of the application then you can use vbscript to uninstall the previous version and install the current one.

FYI - This was the ultimate solution. Thanks.
Answered 11/25/2011 by: Valiante
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity