Open wixbot opened 10 years ago
Document existing behavior across related-bundle action types first.
Draw pretty diagrams with Mermaid.
As discussed in the meeting, this behavior was intentional. Bundles A and B are "publishing" Bundle C's upgrade as their own in order for Bundle C to block itself from downgrading Bundle A or B. Ironically, this functionality is not in the engine. It relies on Bundle C's BA to block the install. Which it might not be doing, given that WixBA doesn't blocks downgrades (except for disabling the button in full UI) and most people built their managed BA from WixBA.
We're leaving this open to consider adding new functionality to specify an upgrade code that will only uninstall bundles with the target code, without "publishing" it as its own upgrade code.
If you have two unrelated bundles A and B, that both are related to a bundle C, A detects B as related bundle (and vice versa) because of the above mentioned registry key.