Hello,
I'm attempting to set up a step in my TestStand sequence that compares the deployment version that's running to a released software configuration, so when the configuration is updated, TestStand sequences exit out and request to be updated. To do this, I need to programmatically identify the version number of the installed TestStand sequence.
What I've come up with is that I can use a custom command in the deployment utility to copy the nidist.id file from <InstallerDir> to "<InstallationDir>\ProjectName\LabVIEW". Like another person who's had an issue here, I can run my command in a CMD window without issue, but the installer yields:
"Error code:2 occurred on command <InstallerDir>\copy nidist.id "<InstallationDir>\ProjectName\LabVIEW"
The system cannot find the file specified."
Similar to the other poster, I find that putting all commands into a batch file is a little ham-fisted, but I also suspect the batch file will not resolve <InstallationDir>, reducing its dynamic functionality.