Thanks, Bob. It looks like the current bootstrapper calls msiexec.exe, rather than using the APIs. I inherited the code and it looks like it was done that way to make it convenient to pass command line arguments, among other things.
If I continue to call the executable, I assume that I'll need to choose the correct msiexec.exe (system32 for 64-bit on x64, syswow64 for 32-bit on x64, system32 on 32-bit), or can x64's system32\msiexec install 32-bit MSIs? -kevin On Jan 23, 2008, at 7:46 PM, Bob Arnson wrote: > Kevin Richardson wrote: >> Is it "OK" to bundle both MSIs into a single, 32-bit, bootstrapper >> executable? >> >> Of course, I'd need to add logic to the executable to install the >> correct architecture's package, but my question is about whether >> the correct processes will be called. Will Windows (and the MSI >> APIs) "do the right thing" depending on the platform specified in >> each MSI? >> > > Yes, just detect the platform and kick off the appropriate package. > MSI is 64-bit and 32-bit on x64 OSes. > > -- > sig://boB > http://joyofsetup.com/ > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
