That's my plan for the WiX bootstrapper. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thielen Sent: Saturday, December 09, 2006 11:06 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Single deployable bootstrapper EXE in 7Zip selfextracting archive
Hi; Is there a way that the original setup.exe can be set as run-once when Windows boots so that after the reboot it starts from the beginning? That would be ok because at that point everything is installed and it then runs your installer. ??? - dave David Thielen www.windwardreports.com 303-499-2544 x1185 Cubicle Wars - http://www.windwardreports.com/film.htm -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jesse Englert Sent: Friday, December 08, 2006 5:27 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Single deployable bootstrapper EXE in 7Zip selfextracting archive How does one create a single EXE to distribute to customers that installs a WiX built MSI and handles the necessary bootstrapping (i.e. installing Windows Installer, .NET, etc....). I came close to the following solution but failed due to Windows Installer 3.1 requiring a reboot: I would like to install an MSI(setup.msi) that is dependent on Windows Installer 3.1. I have a bootstrapper (setup.exe) to install Windows Installer 3.1 before installing the MSI. The bootstrapper(setup.exe) expects the MSI(setup.exe) and the Windows Installer 3.1 redistributable to be in the same directory as the bootstrapper(setup.exe). So, I am using a 7Zip self extracting archive to package the MSI(setup.msi), bootstrapper (setup.exe), and Windows Installer 3.1 redistributable. The 7Zip archive will self extract when double clicked into a temp directory and start the bootstrapper(setup.exe). The problem is that Windows Installer 3.1 redistributable requires a reboot so the temp directory is deleted during the reboot. When Windows restarts, the bootstrapper(setup.exe) picks up where it left off and tries to run the MSI(setup.msi). The MSI(setup.msi) is no longer there due to the temp directory being deleted during reboot. Any insights on how to solve the issue of having to reboot or creating a single deployable exe? -Jesse ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE V _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
