Confusion over Engine VersionString

[Richard.Morgan]

I downloaded and installed the lastest 4.0.1f Patch (which wonderfully fixes my variables view window) and wanted to put some code in my program to disable the variables view if the version of TestStand the user is running is less than this patch.  When I retrieve Engine.VersionString, the value is 4.0.1f1 (4.0.0.1030) while the MajorVersion is 4, the MinorVersion is 0, and the RevisionVersion is 0.  Why is the Revision 0?  Shouldn't it be 1?  Since I can't seem to find BuildVersion, I have to resort to parsing up the VersionString.  Is there something I am missing?

I can see where having the BuildVersion would be pretty handy since the named version isn't the same as the numbered version.

Any advice would be appreciated.

[Anand_Jain]

Richard,

To answer your question - Why is the Revision 0?
Because 4.0.1 is really an upgrade of 4.0 and not a seperate new version of TestStand. Hence,  the internal version is kept as 4.0.0 for technical reasons.

You could either parse the versionString you get from the engine or use windows SDK to get the version of tsengine.dll.
We are planning to add API to get buildVersion in a future version of TestStand.


Regards
Anand Jain
National Instruments



Message Edited by Anand Jain on 02-07-2008 02:29 PM