You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my MSI I have authored a detect-only package in the upgrade table (to detect the VSTO runtime for use in a launch condition). When burn detects this package (with a product code of "{11538652-E5E4-37F1-86D7-418871E45292}") it calculates the operation as a "MajorUpgrade" instead of "none".
I have attached my exported upgrade table and burn log as requested. I also attached my burn manifest because I noticed the RelatedPackage/@OnlyDetect attribute is set to no instead of "yes" (so at least part of the issue is at compile time).
I'm experiencing this issue with one of my installers that also had a DetectOnly line in the Upgrade Table. Removing the additional Upgrade Table entry has fixed the problem, but there might be a need for such a table entry in the future. The Upgrade Table entry in question was obsolete and easily removed.
This is actually by design: A typical use case for a detect-only Upgrade row is to block a user attempt to downgrade (i.e., detect a later version of the app already installed). Burn uses that to signal that the package being installed is obsolete. So we prevent that for detect-only rows that have an upgrade code different than the package's own upgrade code. There are two cosmetic side-effects: OnlyDetect="no" shows up in the manifest and MajorUpgrade appears in the Burn log. Otherwise, Burn does nothing about the MajorUpgrade operation in the actual plan. (Burn lets MSI deal with the actual work for related packages.) I'll leave this bug open for v3.7 to see if we want to clean up the cosmetics (e.g., by adding 'Unrelated="yes"' or something to the manifest, or dropping the Upgrade row entirely).
Version: 3.6.2928.0
In my MSI I have authored a detect-only package in the upgrade table (to detect the VSTO runtime for use in a launch condition). When burn detects this package (with a product code of "{11538652-E5E4-37F1-86D7-418871E45292}") it calculates the operation as a "MajorUpgrade" instead of "none".
I have attached my exported upgrade table and burn log as requested. I also attached my burn manifest because I noticed the RelatedPackage/@OnlyDetect attribute is set to no instead of "yes" (so at least part of the issue is at compile time).
The text was updated successfully, but these errors were encountered: