Hi Alan,
If the EXE can receive the paths of the text files, you can use a "Launch file or open URL" custom action to launch the EXE with a custom command line. In this case the "Command Line" field from the
Custom Action Properties page can contain the full path to the executable and its parameters (the paths of the text files).
Since the files are in your package, you can use installer properties to define theirs paths. For example, a file installed in "Application Folder" can use this reference as its path:
Please note that the EXE launched by the custom action can also use installer properties for its path. For example:
Code: Select all
"[ProgramFilesFolder]My Folder\MyApp.exe" "[APPDIR]MyFile1.txt" "[APPDIR]MyFile2.txt"
will be resolved to something like this:
Code: Select all
"C:\Program Files\My Folder\MyApp.exe" "C:\Program Files\Your Company\Your Application\MyFile1.txt" "C:\Program Files\Your Company\Your Application\MyFile2.txt"
Since this custom action uses files installed by the package, it should be scheduled after the "InstallExecuteSequence" -> "InstallFiles" standard action. Please note that Advanced Installer allows you to create SQL connections and run SQL scripts through the
SQL Scripts page (this is an Enterprise feature).
Regards,
Cosmin
FOLLOW US
Get the latest news in Application Packaging