Custom data type version number conflicts

[kerugoya]

Custom data type version number conflicts

Options

• Mark as New
• Bookmark
• Subscribe
• Subscribe to RSS Feed
• Highlight
• Print
• Email to a Friend
• Report to a Moderator

07-11-2011 08:10 AM

I am new to Teststand software interface.  While doing my first software release under the guidance of a more experienced colleague, we discovered that Teststand will not run if it detects version number conflicts between custom data types on my machine vs. the production test machine.  I verified differences between all .seq files in my test program directory, but I did not realize that the version number difference exists in the StationGlobals.ini file, which is stored in a different location.  After discovering this, I modified the version number in one of the files.  However, two releases later, I discovered that the version number mismatches in another two files.  This raises several questions for me :

1.  Is there a way in Teststand to view all the .seq files where a custom data type is used and then change its version number in one attempt?

2.  Under what instances does Teststand upgrade the version number of a custom data type?

3.  Are there any tools or scripts within Teststand that can allow the version number of custom data types to be changed in all .ini files when a difference is discovered between the current production test station settings and a new release?

Please help.

[kerugoya]

I am new to Teststand software interface.  While doing my first software release under the guidance of a more experienced colleague, we discovered that Teststand will not run if it detects version number conflicts between custom data types on my machine vs. the production test machine.  I verified differences between all .seq files in my test program directory, but I did not realize that the version number difference exists in the StationGlobals.ini file, which is stored in a different location.  After discovering this, I modified the version number in one of the files.  However, two releases later, I discovered that the version number mismatches in another two files.  This raises several questions for me :

1.  Is there a way in Teststand to view all the .seq files where a custom data type is used and then change its version number in one attempt?

2.  Under what instances does Teststand upgrade the version number of a custom data type?

3.  Are there any tools or scripts within Teststand that can allow the version number of custom data types to be changed in all .ini files when a difference is discovered between the current production test station settings and a new release?

Please help.

[~jiggawax~]

Have you read this?  http://zone.ni.com/devzone/cda/tut/p/id/7060

I can tell you that your situation is not uncommon with TestStand.  The key is just doing it right the first time.  haha

#1- I doubt that this is possible because then TestStand would have to know every location of every .seq on the machine.  You will only see it when you open the sequence file.

#2- TestStand updates the version every time you change it.  You should get a message popup when you try to save that asks if you want to increment the version or not.  There's also a check box that says Remove Modified Mark From Types.  Look under Station Options in the File tab.  There are some settings there about Type conflicts.

#3- http://zone.ni.com/devzone/cda/tut/p/id/7910

http://digital.ni.com/public.nsf/allkb/4153576DA04BEB098625743D00704A09

Hope this helps,