I'm aware of similar questions in WiX MSI, but I'm having issues starting an application within a bootstrapper EXE file created with Burn after the installation. My full bundle is below.
If it makes any difference to the scenario, the bootstrapper is started in passive mode, so the user shouldn't need to press anything.
<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"
xmlns:bal="http://schemas.microsoft.com/wix/BalExtension"
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension">
<Bundle Name="My Company AutoUpdater"
Version="1.0.11"
Manufacturer="My Company"
UpgradeCode="--GUID--">
<BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.HyperlinkLicense">
<bal:WixStandardBootstrapperApplication SuppressOptionsUI="yes"
LicenseUrl=""
LogoFile="logo.png" />
</BootstrapperApplicationRef>
<Chain>
<MsiPackage SourceFile="..\App1\bin\Release\App1.msi" />
<MsiPackage SourceFile="..\App2\bin\Release\App2.msi" />
</Chain>
</Bundle>
<Fragment>
<Property Id="WixShellExecTarget"
Value="[#C:\Program Files (x86)\My Company\App1.exe]" />
<Binary Id="MyCA"
SourceFile="[#C:\Program Files (x86)\My Company\App1.exe]"/>
<CustomAction Id="LaunchApplication"
BinaryKey="MyCA"
ExeCommand="-switch"
Execute="deferred"
Return="check"
HideTarget="no"
Impersonate="no" />
<InstallExecuteSequence>
<Custom Action="LaunchApplication"
After="InstallFiles" />
</InstallExecuteSequence>
</Fragment>
</Wix>
Use the advice given in the WiX manual, How To: Run the Installed Application After Setup. There is a built-in WiX extension that will handle this for you. You should be able to reference the WiX Util extension, add the following code to your project (replacing the value of the property of course), then schedule the action to run:
You can add a variable to your Bundle called "LaunchTarget" with a path to the executable you want to run:
After the install, the Setup Successful screen will display a "Launch" button that will start your app.
It had a number of steps. Remember I was running this from a bootstrapper, not an MSI file, whereby levarius's answer would have sufficed.
Basically, I removed any of the launch logic that was posted in the original question, and created a new package, whose sole functionality was to kick off an application (using a custom action), and whose location had previously been saved in the registry - that is, the application running when it found that an update was available, set this item in the registry.
The package (called PostInstall below) is then run ONLY if one of the other packages has been installed previously - found by the existence of a key in the registry (set in each product's MSI). This means that no application will be started automatically after a new install has completed.
The following is from the bootstrapper bundle (WiX 3.6 in my case)