Hi there... I've created my own bootstrapper that is able to read a series of MSI paths from an ini file in order to appropriately launch a series of installers in a defined sequence.
On very clean machines the package I'd like to come first can create a reboot request on the system, but I have overcome this by adding the REBOOT property set to ReallySupress in a transform that is aplied to all but the last package. In my experience this does the right job for all packages, and then on the last one I allow the reboot if it was earlier set to do so - as far as I can tell this works beautifully. However, I have found on another forum that setting REBOOT in this way stops subsequent MSI's from running until the reboot request has been satisfied: http://www.appdeploy.com/messageboards/tm.asp?m=408 Has anyone have any experience of this, perhaps particular versions of Windows Installer are affected? Cheers, G -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-Installers-with-a-reboot-tp6077788p6077788.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
