09-10-2015 08:11 AM
Hi,
I've inherited code which uses Teststand custom steps from a 3rd party vendor.
Over time the custom steps have been updated and so the PC's in use have different versions of the 3rd party custom steps.
(The custom step names remain the same, but the supporting dll's are updated.)
My question is: if write a sequence incorporating a 3rd party custom step on one PC, if I run the same sequence on a second PC,
how do I know the custom step will use the same intended dll which supports the 3rd party custom step ?
I appreciate that dll's have an inherent problem due to the fact that they are distinguished by name.
Any tips appreciated, thanks,
Gary
09-14-2015 06:34 AM
Hi Gary,
I think the best option is using the TestStand Deployment Utility, plaese see:
http://digital.ni.com/public.nsf/allkb/EE3382373D209449862570A5006572F0
This should make sure that all necessary files are included and that the dependencies are kept intact. To avoid naming conflicts it is probably best to use different names for the updated dll:s.
/Anton
09-15-2015 01:46 AM