I’m really stumped on a failure rollback scenario with multiple MSI’s bundled
in a WiX bootstrapper.
Consider the following WiX bundle chain:
<Chain>
<MsiPackage SourceFile="a.msi" />
<MsiPackage SourceFile="b.msi" />
</Chain>
a.msi creates a few files in C:\Program Files (x86)\a
b.msi creates a few files in C:\Program Files (x86)\b
[Step 1]: A computer has a complete working version 1 installed. (Version 1
bootstrapper, Version 1 a.msi and Version 1 b.msi)
[Step 2]: Upgrade to version 2 (Version 2 bootstrapper, Version 2 a.msi and
Version 2 b.msi) but b.msi has a condition that fails and will property trigger
a rollback for the entire bundle.
[Step 3]: The files associated with the upgraded a.msi are removed from the
install directory and things are not left in a version 1 working state. Almost
as if since a.msi upgraded to version 2 without any issue the previous version
1 got removed never to return automatically back to the installed version 1.
Rolling back just uninstalls version 2 of a.msi and never reinstalls version 1
of a.msi.
[Manual Workaround]: A workaround is to manually go into the Control Panel,
Programs and Features and repair the entire installed version 1 bootstrapper to
have the lost files of version 1 a.msi reinstalled.
Is there something I’m missing to get my bootstrapper chain to rollback to the
previous version 1 working installed state?
Or is this a known WiX bug? Is the following bug the issue I’m having?
http://sourceforge.net/p/wix/bugs/2766/
Any help would be fantastic, thank you!
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
