CODEWITHSUNDEEP
wix
PlTaylor
PlTaylor

Reputation: 7525

Why doesn't this silent launch work in WIX?

I have the following command running at the end of my package install for an application.

<Property Id="WixShellExecTarget" Value="[INSTALLDIR]RCR.VDS.exe" />
<CustomAction Id="LaunchApplication" BinaryKey="WixCA"
      DllEntry="WixShellExec" Impersonate="no" />

I can't use [#myApplication] because I run heat on my output folder on my build server so I don't know the auto generated id of my application. Any ideas on how to silently run my application after the install?

The log file shows this for the command line section

******* CommandLine: **********

MSI (c) (30:74) [09:47:14:156]: Note: 1: 2203 2: VDSInstall.msi 3: -2147287038 MSI (c) (30:74) [09:47:14:156]: MainEngineThread is returning 2

Upvotes: 2

Views: 1038

Answers (2)

Rob Mensching
Rob Mensching

Reputation: 35996

The are a copy things you can consider:

  1. The identifier from heat.exe will be stable. So you can use the ugly identifer in your [#UglyFileId1234abcef45612345asdf] custom action.

    a. You could also apply a XSLT to transform the heat output for the executable file's Id to something nicer than the ugly identifier. Depends how readable you want the launch custom action to be.

  2. If you want the executable launched silently then you'll probably want the Quite Execution custom action instead of the Shell execute custom action that "LaunchApplication" uses.

Upvotes: 1

Christopher Painter
Christopher Painter

Reputation: 55601

Please see: How To: Run the Installed Application After Setup

If you want the custom action called during a silent install add:

<InstallExecuteSequence>
  <Custom Action="LaunchApplication" After="InstallFinalize">SOMECONDITION</Custom>
</InstallExecuteSequence>

Note SOMECONDITION should be an expression that checks the EXE is installed and the user wants the program to be launched.

Upvotes: 2

Related Questions