|
From: Jesse E. <jen...@at...> - 2006-12-09 00:25:30
|
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 |