On 12/20/2013 02:01 PM, Rob Mensching wrote: > It seems there is a bit confusion how executables are launched. Here are > things a bit simplified. > > Eventually it all comes down to something below ::CreateProcess() that only > launches PE-files (.exe and .coms).::CreateProcess() will fail if you pass it > a .bat file or .doc file or anything else you're used to double click and > launching. However, you can use ::ShellExecute() which will do a look up > based on the extension and find the .exe (or .com) that is registered for the > extension. In the case of .bat files, cmd.exe is launched. > > With that understanding, the Windows Installer launches executables using > ::CreateProcess(). Which explains why you can't pass a .bat file and have to > use cmd.exe. However, unless someone's done something extremely weird (that > I can't really imagine) there is no reason an executable (a .exe or .com) > must be launched from cmd.exe.
Ok, that's good to know how the installer is launching things. I'll test and see if the exe can be launched 'implicitly' without cmd.exe and see if the system will figure out that it needs cmd.exe. The main problem though is that the installer is eating the quotes off the first argument in ExeCommand. And that could affect more than just trying to run cmd.exe with arguments. > > -----Original Message----- > From: Edwin Castro [mailto:0ptikgh...@gmx.us] > Sent: Friday, December 20, 2013 10:38 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces > > On 12/20/13, 10:27 AM, Gerry Reno wrote: >> I not certain this will work. It might with something like a .bat >> file since the system knows that .bat files are executed by cmd.exe. >> >> But what is there to tell the system that my exe requires being run by >> cmd.exe? > Assuming that your exe is really a compiled executable, then the PE file > format of the exe itself tells windows whether it is a windows subsystem > executable or a "command line" subsystem executable (I'm forgetting the > actual terminology). Windows determines the subsystem to use when it loads > the exe just prior to execution. > > -- > Edwin > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
