In attempt to add custom action, I can create a new custom action of type Launch EXE with working directory by clicking the + button (no sequence) in the add custom action window. OK, no problem, I then see a dialog in which to enter File Path, Command Line, and Working Directory.
The executable that I would like to install is an app to allow user to setup up and test configuration settings, and produced a configuration file for the main target of the installer.
The executable configuration app is installed in the application folder as directed for Resources->Files and Folders.
1) When I enter [APPDIR] in file path text box, it show up red. No jagged underline, but definitely red.
The action apparently is named LaunchExeWithDirectory, this name appears in Custom Behavior->Custom Actions->Existing Custom Actions tab.
2) I cannot cut and paste LaunchExeWithDirectory to any installation stages, and it is not attempted during install, and the install fails. There is no reference to the custom action in the verbose installer log.
Sound familiar? Thanks.
FOLLOW US
Get the latest news in Application Packaging