I am having no success in modifying a Windows Installer MSI to run a batch file after the primary output has been installed. I have searched for this and found many suggestions, but nothing that works.
Windows Installer cannot launch batch files directly by using installed or attached custom actions. However, in Advanced Installer you can run a CMD or BAT file through a Launch file predefined custom action. In the case of a 64-bit CMD or BAT file you can just enable the option Use 64-bit Launcher.
What you said above is incorrect:
Custom actions can only be executable files. A batch file is not executable.
Custom Actions (even without tools like InstallShield) can be .EXE, VBScript, JScript, or DLL based. If you write a DLL, you can write whatever code you want to call a batch file or make any changes you want to the system -- there is no limit.
Update: an example that worked for me: (entry in CustomAction table)
Action Test
Type 34
Source SystemFolder
Target cmd.exe /c c:\test.bat
ExtendedType <blank>
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With