[wix-users] Burn automatic rollback on installer failure

[Blair Murri]

I would have expected that you would have needed to repair only MSI #1, not both. The MSI with the error should have restored the system, it's an error in that MSI if that's not the case.



Running a single repair to the installed bundle should have fixed everything without having to go to each MSI separately.



Blair Murri



Sent from my Windows 10 phone



From: Tyler Gustafson<mailto:tgustafson at solacom.com>
Sent: Tuesday, January 24, 2017 8:01 AM
To: WiX Toolset Users Mailing List<mailto:wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Burn automatic rollback on installer failure



And I've found where I read about this before:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-multiple-MSI-s-don-t-rollback-to-a-working-installed-state-td7586867.html

Sorry for the spam. If anyone knows about any new developments to this please let me know.

Tyler

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Tyler Gustafson
Sent: January-24-17 10:49 AM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Burn automatic rollback on installer failure

I feel like I've read about this somewhere before but I can't find it now. I just wanted to confirm this is expected behaviour.

I've got a burn bundle using out of the box burn functionality.
The bundle installs 3 msi files in order 1, 2, 3.

I do minor upgrade to each of the msi and re-bundle them but this time I've put a custom action in msi #2 which causes the installer to fail.

When I run the this new bundle it does a minor upgrade to 1, starts a minor upgrade to 2 and fails triggering a rollback to both 1 and 2. It never attempts to upgrade 3.

So far all works as I would hope but now I find that I have to go into Add/Remove programs and manually repair products 1 and 2 to get them back to the version they were told to roll back to.

I feel like I've read that the burn engine doesn't do the automatic repair by design but I can't remember where I saw that. If this is the case and I want the engine to automatically repair would I have to write my own custom bootstrapper code or am I missing something to automatically get this functionality?

One last piece of the puzzle that might be important is I am using <MajorUpgrade DowngradeErrorMessage="A newer version of [ProductName] is already installed." Schedule="afterInstallExecute" /> In my msi.

Thanks,
Tyler



____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/