Migrating from EXE to MSI doesn't uninstall old bootstrapper from Control Panel

[nrcaliendo]

I'm not a WiX expert, so I apologize if my WiX vernacular is lacking. I've been tasked with migrating our app's installer from an EXE to an MSI, and I'm running into this problem...

Previous versions of our application installed using an EXE that bundled a custom UI bootstrapper, a .NET Framework 4.8 preqreq package, and the app's MSI.

For the sake of this discussion, let's call these versions 1, 2 and 3. Starting with version 4, our stakeholders want an MSI install only (no custom UI, no .NET prereq).

The problem is when I upgrade the app from, for example, version 3 to version 4 by running the version 4 MSI, the app seems to upgrade successfully, but I'm left with two entries in Add/Remove Programs (ARP) in Control Panel. For example:

My App 3.0
My App 4.0

Likewise, if I uninstall My App 4.0, the My App 3.0 ARP entry remains.

I assume the My App 3.0 ARP entry is associated with the version 3 bundle, which has its own product upgrade code. What is the recommended way of ensuring these old ARP entries get removed when upgradig via the new MSI?

[robmen]

Easiest way is to use the MajorUpgrade element. Deployment Dojo S1:E4 - Out with the Old. In with the New is the beginning of a few episodes where I explore upgrades.

[nrcaliendo]

Thanks for your response. I watched your video and tried your suggestion, using <MajorUpgrade AllowSameVersionUpgrades="yes"... />. This did not fix my problem. The My App 3.0 ARP entry still remains after uninstalling version 4.

Again, it seems as if the My App 3.0 ARP entry is associated with the version 3 bootstrapper. In fact, inside my Bundle.wxs file, the bundle has its own ProductUpgradeCode:

This ProductUpgradeCode is different than the one for the product itself:

I'm not sure if these are supposed to be the same?

[robmen]

Sorry, my mistake. I was answering a different question, not the one you asked.

There isn't anything built in that will uninstall/upgrade a bundle from an MSI.

[nrcaliendo]

OK thanks, I think I'll probably have to write some custom action.