I have a package that is version 2.0 and my cilent would like to have the latest verison which is 2.2 because that is the verison the vendor will support. So, my question is if i'm doing the right procedure by taking the 2.0 package, changing only the product code(leaving the upgrade code alone) and replacing/adding the files required to have a 2.2 package? Now the problem i do see here is that when you go to add/remove programs, there are now both the 2.0 and 2.2 packges listed. Is this suppose to be there?
0 Comments   [ - ] Hide Comments


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.
Answer this question or Comment on this question for clarity


You are part the way there [;)]

In the v2.2 package you have created you need to check that the value in the ProductVersion property has been incremented and then make sure the 2.2 package has an Upgrade Table. This table, as a bare minimum, should containing the following entry :

Upgrade Code : <Enter the GUID held in the UpgradeCode property>
VersionMin : <leave this completely blank>
VersionMax : <value of ProductVersion property in your v2.2 package>
Attributes : 0

If VersionMin is set to blank and Attributes is set to 0 this will means that all previous versions of the package up to but not including v2.2 will be removed when v2.2 is installed.

For more documentation on the Upgrade Table try here


Answered 05/15/2007 by: spartacus
Black Belt

Please log in to comment
And also the removeexistingproduct action in Execute immediate of the msiscript should be inbetween, "InstallInitialise" and "InstallValidate"
Answered 05/15/2007 by: bheers
Second Degree Blue Belt

Please log in to comment