Hi,
Can I use a batch file to run as an attached Custom Action?
If so, how do I do this?
I've been trying to setup a batch file to run as an attached custom action during the Begin stage but it's not working.
In the Command Line field, I only added a parameter as a property and left the Execution Condition field empty.
Suggested Articles
Hi,
Atached custom actions can have as source an EXE, a DLL, or a VBScript or a JavaScript. No BAT. You can run a bat file as an installed custam action (the bat file is a file installed by your package). For this select "Add Predefined Custom Action"->"Lanuch File or Open URL" from the context menu and edit the command line of this custom action to be a formatted string that expands in the full path of the bat file (Edit buton->Insert Reference to File).
Regards
Atached custom actions can have as source an EXE, a DLL, or a VBScript or a JavaScript. No BAT. You can run a bat file as an installed custam action (the bat file is a file installed by your package). For this select "Add Predefined Custom Action"->"Lanuch File or Open URL" from the context menu and edit the command line of this custom action to be a formatted string that expands in the full path of the bat file (Edit buton->Insert Reference to File).
Regards
Hi,
The custom action will be executed before the installation, even if it is of installed type.
You can schedule another custom action to delete this BAT file at the end of the installation, but this won't solve the problem completely, as the file will reappear in the case of a repair process.
The last solution, if you want to run this BAT as an attached custom action you could use a workaround. You can create an EXE that generates this BAT file in a temporary folder on the disk and then launches it. After the BAT execution is over the program deletes it from this temporary location.
All the best,
Mihai
The custom action will be executed before the installation, even if it is of installed type.
You can schedule another custom action to delete this BAT file at the end of the installation, but this won't solve the problem completely, as the file will reappear in the case of a repair process.
The last solution, if you want to run this BAT as an attached custom action you could use a workaround. You can create an EXE that generates this BAT file in a temporary folder on the disk and then launches it. After the BAT execution is over the program deletes it from this temporary location.
All the best,
Mihai
Thank you Mike, but my question is how will this installed custom action script be executed in a pre-installation stage before it even gets installed?
I tried running it as installed type but it wasn't working and I assumed that the reason for it is that the installer cannot find the bat file. Is my assumption correct?
I tried running it as installed type but it wasn't working and I assumed that the reason for it is that the installer cannot find the bat file. Is my assumption correct?
Hi,
You are right, if an installed custom action is conditioned to run in the install phase then it will not run if scheduled before the "InstallFiles" standard action.
Similarly, if it is conditioned to run on the uninstall phase, it will not run if scheduled after the "Uninstall" standard action.
Regards,
Mihai
You are right, if an installed custom action is conditioned to run in the install phase then it will not run if scheduled before the "InstallFiles" standard action.
Similarly, if it is conditioned to run on the uninstall phase, it will not run if scheduled after the "Uninstall" standard action.
Regards,
Mihai