04-07-2008 01:12 AM
Hi Rick,
I think you miss understood my response.
I was referring the the set of VI's that are shipped with TestStand in the Tools\Depolyment folders.
There is quite a bit of code that is shipped with TestStand that allows the user the ability to customise TestStand.
I was going to look at adding to the error message the actual VI that the deployment tool was having a problem with.
Regards
Ray
04-07-2008 03:10 AM
04-07-2008 03:22 AM
04-09-2008 10:38 AM
Mehran,
I was able to open the test file- but I was missing the assembly that it used so I could not test it directly. I made up two similar test VIs- one that invoked a method from an assembly from the GAC and one that invoked a method from a private assembly. I was able to deploy both VIs using TestStand 4.0.1 and LabVIEW 8.5.1. If you want to attch the assembly I can try deploying you test VI. Is your assembly in the GAC? If not what is the relative path between the VI and the assembly?
-Rick Francis