04-09-2010 04:21 PM
04-12-2010 11:09 AM
John -
When you say that it bombs out, I'm assuming that you encounter an error when running the installer on the target machine. If this is correct and you are using TestStand 4.1.1, you may be encountering an issue addressed by the following patch:
Installer built with Deployment Utility and including custom commands crashes
Hope this helps.
04-12-2010 11:56 AM
04-12-2010 03:11 PM
This is how I use the Custom Commands window from the TestStand Deployment Utility:
Create a batch file and put your command in the batch file. Add the batch file to your workspace file and project. Deploy it to the installation directory.
Then set the Custom Commands window to the following attached picture. I always check the box 'Show Command Progress Window' as this sometimes give a clue to what happens when things go wrong!
Thanks,
Paul Holzrichter
12-03-2015 03:56 PM
Sorry to bump an old thread, but has this been fixed in the main TS install? I ask because I'm triyng to do the exact same thing, and running into an error.
Specifically, run mkdir "C:\Existing Directory\New Directory".
I've tried running the command on the machine via the command line, and it works, so it's not a persmissions issue.
And it seems unnecessarily complex to run a command to run a batch file that just runs another command.
I'm currently using TestStand 2014 SP1.
04-12-2016 03:57 PM
So posting this for the sake of including the solution if someone else searches for it in the future.
To get standard command line commands to work in the custom commands window, here's what you have to do:
Command Directory: None
Commands and Arguments: cmd.exe /c mkdir "C:\Existing Directory\New Directory"