Having a strange problem. We have several windows .bat files in the installer, to do specific tasks. When the installer runs, their name doesn't get resolved. Error message is something like "Cannot find c:\Program."
Our app is going into c:\Program Files\etc. One subdirectory has our .bats. Set it up like this:
Custom actions
Clicked custom action wizard
Selected "open another kind of file"
Selected "a file installed by this package"
Navigated to the .bat file, clicked OK
Commit, next, finish
The Custom Action Properties screen appeared.
Source Path: <viewer.exe>
Source Type: Executable (*.exe)
Command Line: [#our_bat.bat]
Selected execution property async, don't wait for return. Execution option commit.
Build went fine. Copied the installer to our test machine, ran it, got the "Cannot find c:\Program" error.
Tried "[#our_bat.bat]", ["#our_bat.bat"], no go. Changed the command line to "C:\Program Files\ ..... \our_bat.bat", that worked. But, if we ever change the installation directory, the hardcoded command line is one more thing to remember. How can AI run .bat files if the path has a space, like Program Files does?