Burn 3.x assumes that installed detect-only related packages that don't match upgrade code are always major upgrades

[wixbot]

Not the burn engine's fault, the 3.x binder lies to the engine. The 4.x binder doesn't lie, so this particular bug doesn't afflict that branch.

It seems that the 3.x binder wanted to make sure that "unrelated" related packages would never be detected as downgrades, so it forces the OnlyDetect flag in the engine's manifest to "no", which the engine interprets as "major upgrade". As a consequence, I have to record in my BA the upgrade code for each and every MSI package, so that I can filter the incorrect information that the engine feeds to my BA.

Originally opened by bmurri

[wixbot]

The original bug is http://wixtoolset.org/issues/3643/. I think there was concern about custom BA's relying on the current 3.x behavior so the change was only made v4.0.

Originally posted by rseanhall

[wixbot]

http://wixtoolset.org/issues/3643/

Taken in v4.0. Can't really take in v3.x, I think.

Resolution set to duplicate
Status changed from Untriaged to Resolved

[wixbot]

FYI, the Upgrade Code (among other useful information) was put into BootstrapperApplicationData.xml in v3.9 so you shouldn't have to hardcode them in your BA.

Originally posted by rseanhall