> 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?
In my bootstrapper I just do CreateProcess(NULL, "msiexec /i xxx", ...) and it does the right thing on both x64 and x86. Regards, John ------------------------------------------------------------------------- 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
