Reputation: 3502
I have a bootstrapper application with several msi packages in the chain. For convenience, the msi packages always perform a major upgrade that completely removes a product before the new version is installed.
When a rollback is necessary during an upgrade operation in the middle of the bundle's chain, the previously performed major upgrades are reverted resulting in the affected products not being installed any more.
This seems reasonable but is probably not what the end user expects. Instead of some products being left uninstalled, those products should be ideally reverted to their previously installed versions.
I wonder if their is a way to solve this requirement without giving up the major upgrade strategy. Can a WiX bootstrapper rollback major upgrades in a way the end user expects?
Upvotes: 2
Views: 658
Reputation: 7127
I had the same question and opened a support ticket with FireGiant. Their response was:
Unfortunately, Burn doesn't do that today. Bundles only carry "their" packages, not older ones. And bundle version N could upgrade version N-1 or N-10 so it wouldn't be feasible to repair one package. Instead, the current best advice is to tell the user to run repair on the already-installed bundle. There's an open feature request to have an option to tell Burn to do that automatically but it hasn't been implemented.
Upvotes: 1