Ahh, that makes sense. Yes, if you use the "JoinTransaction" functionality of the Windows Installer you'll get exactly that behavior.
Burn doesn't use that transaction functionality because we found enough bugs that we bailed on it. No Microsoft products (that I'm aware of) use the feature which is typically a very good sign to, "Yeah... not going to use that." I think there is still a comment in Burn saying "this is where Msi Join Transaction stuff goes" but the current Burn transaction behavior has proven quite stable so not sure when/if we'd bother implementing it. _____________________________________________________________ Short replies here. Complete answers over there: http://www.firegiant.com/ -----Original Message----- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Friday, October 10, 2014 11:42 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Shortcut creation seems to cause sxs assembly error in Event Viewer An InstallShield chain of MSIs is the "single transaction" install, the multi-package transaction where the whole transaction of multiple MSIs isn't committed until the end. That seems to include committing assemblies into the GAC, that's not MsiPublishAssemblies as much as the Fusion API not doing the commit until InstallFinalize. That's the context, I assume, and it looks like some things in the install aren't working until that final MSI Commit at the end of the transaction. --------------- Phil Wilson ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
