Home/ Questions/Q 6021533
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T03:43:37+00:00

In a Setup project the executable files such as .exe , .dll , .js

  • 0

In a Setup project the executable files such as “.exe , .dll , .js , .vbs” are acceptable but there is no way to run a .bat file in a Custom Action.

The question is how to run the *.bat files during installation?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Well, after much searching and trial and error I have solved this. I’m not sure if this is the best way, but it works.

    Here’s the scenario: I have an application I would like to deploy via a Visual Studio Setup project. In addition to my application files, I would like to create a subdirectory in the target directory that contains a batch (.bat) file. I would like this file to run at the end of the installation process.

    Here’s what you do:

    1. Create a setup project and configure as you normally would, including the subdirectory in which you’ll place your batch file (you can just place it in the Application Folder directly if you don’t want it in a subdirectory).
    2. In the "File System" view (right-click on the project in Solution Explorer->View->File System), add the batch file you want to execute and cmd.exe (C:\Windows\System32\cmd.exe)
    3. Open the "Custom Actions" view (right-click on the project in Solution Explorer->View->Custom Actions)
    4. Right-click on "Commit" and choose "Add Custom Action"
    5. Navigate to and select cmd.exe.
    6. Open the properties panel for the newly created custom action.
    7. Delete /Commit from the Arguments property.
    8. Enter: /c "[TARGETDIR]subdirectoryname\batchfile.bat" in the Arguments property, where subdirectoryname should be replaced by the name of your subdirectory (if you put the batch file in a subdirectory like I did… if you didn’t, the value should be /c "[TARGETDIR]batchfile.bat") and batchfile.bat should be the filename of your batch file.

    That’s it. The batch file will now be executed once the rest of the installation process is completed.

    Here’s an example for the sake of clarity:

    My batch file: blah.bat
    My subdirectory: mydir

    The value of the Arguments for my custom action targeting cmd.exe would then be

    /c "[TARGETDIR]mydir\blah.bat"

    • 0