Hi Thanks for your answer. Having a launcher exe seems to be the save way to go. In the meantime, i noticed that on some machine it works as supposed, using the following custom action definiton:
<CustomAction Id="LaunchPrintProcessAction" Directory="PrintProcessDir" Return="asyncNoWait" ExeCommand="[PrintProcessDir]PrintProcess.exe -autostart" /> However, i think we still have to use the launcher as we have to ensure it has to work on all machines. Regards ________________________________________ Von: Dan Vasilov [...@rms.ro] Gesendet: Mittwoch, 14. Juli 2010 07:51 An: wix-users@lists.sourceforge.net Betreff: Re: [WiX-users] Calling an exe file upon installation (works but either cmd remains open, or installation does not finish) I would use a launcher .exe that can properly be launched from the setup. Then this launcher would start your application. Probably your executable has some particularity, the setups we've developed with Wix properly launch the main executable. Dan ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
