05-11-2015 05:09 PM
I seem to be missing something in how the various version numbers are supposed to be used. My end goal is to log and possibly display in the UI the version of the sequence and which installer version was used to inspect a UUT. I have gotten most of the way there using:
How Can I Programmatically Query the Sequence File Version of My TestStand Sequence?
and logging this into the report with a function which contains:
Parameters.UUT.AdditionalData.SetValString("Test Version",1,RunState.SequenceFile.Data.Version), Parameters.UUT.AdditionalData.SetFlags("",0,PropFlags_IncludeInReport)
The "Deployment Version" in the TestStand Deployment Utility auto incrementing the 3rd position of a version number while the sequence auto increment is working on the 4th.
My first question is are these 2 version numbers in anyway supposed to be related to each other? As it seems to me you would want those 2 reversed, I can make several installers based on sequence version X, making changes to what supporting files are also installed.
If they are not related as I suspect that they are not. How do I programatically grabed the installer version and also log that into the result report?
is there an option to perform a custom deployment build step to log the deployment version before it builds and then reference that log at runtime of the test?
05-12-2015 12:33 AM
Hi,
The sequence file version and deployment versions are not related.
You can build the installer with whatever version you want using the command line :
https://decibel.ni.com/content/docs/DOC-38947
Hope this helps,
Ravi