Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have two products installed. They have the same version number and upgrade code, but different product code. I would like to do a major upgrade on one of these products, but the upgrade exe that I created ends up removing both products, and installing new one.
That being said, how can I keep one product installed when the product has the same upgrade code with the another product that I would like to upgrade?
The Upgrade table first drives FindRelatedProducts. FindRelatedProducts uses the information to perform MSI product searches. If places the ProductCode of a found in the property specified by the ActionProperty column
Later, RemoveExistingProducts performs an uninstall of any ProductCodes found in any ActionProperty properties ( provided that msidbUpgradeAttributesOnlyDetect is not set ).
So the trick out of a sticky situation like this is to author an Upgrade row that will cause FindRelatedProducts to not find either product. Then use a custom action to do your own searches and set the properties as needed ( one but not the other ). Now RemoveExistingProducts will be able to perform the major upgrade.
As a side note: this is a work around and not a best practice. Carefully consider your choice of UpgradeCodes, ProductCodes and ProductVersion properties to avoid this situation in the future.