Many moons ago we stopped adding a 'launch the installed app' check box to our final dialog as we had intermittent issues with the launched app window appearing behind other windows as per this WiX mailing list issue from 2005: http://sourceforge.net/p/wix/mailman/message/11428915/ We didn't implement the coding fix that was suggested there.
At that time we were using a Custom Action: <CustomAction Id="LaunchProduct" FileKey="ApplicationExe" ExeCommand="" Return="asyncNoWait" /> Now the WiX CHM suggests using a WiX a Standard Custom Action http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/run_program_after_install.html in WiXCA: <CustomAction Id="LaunchApplication" BinaryKey="WixCA" DllEntry="WixShellExec" Impersonate="yes" /> </Product> Does anyone know if any efforts to sidestep the above issue were made when making this a 'Standard Custom Action' in WixShellExecTarget? Or if not, do people using WixShellExec to do this commonly experience this issue with their apps now (hard for me to test as it was intermittent)? Many Thanks Matt ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
