06-16-2021 09:48 AM - edited 06-16-2021 09:55 AM
Hello all! Utilizing TestStand's Command Line Deployment Build Tool (BuildTSD.exe), shipped with every version of TestStand from version 2013 and beyond (TestStand Command Line Deployment Build Tool - NI Community), I am unable to set the Deployment Version of a TestStand Deployment file (.tsd) utilizing the Build Tool's (BuildTSD.exe) /versionString command line switch. Instead, the command line switch seems to set the Installer Version (the executable artifact built by the TestStand Deployment Utility to actually distribute your test system/solution) of a TestStand Deployment file (.tsd).
(Deployment Version of a TestStand Deployment file depicted above within the TestStand Deployment Utility)
Here is an example:
(The TestStand Deployment file used here includes a TestStand Workspace file (.tsw) with one TestStand Project file (.tpj) within the workspace, and the TestStand Project file includes three empty TestStand Sequence files (.seq))
The documentation for the TestStand Deployment Utility Build Tool (BuildTSD.exe) DOES NOT give a description of the /versionString command line switch:
(https://forums.ni.com/ni/attachments/ni/7324/666/1/BuildTSD%20Documentation.pdf)
Two questions for the community:
Thank you community! Please let me know if you need me to provide any additional details.
All the best,
Erik
06-18-2021 11:34 AM
Hello Erik,
As you correctly noticed, calling BuildTSD.exe /versionString "1.1.0" "MyBuildSpec.tsd" does produce and installer for a Product of a version "1.1.0".
Im curious what is your use case that requires programmatic update of deployment version as it has no impact on the product (installer) built by .exe.
Roman