TestStand Deployment and Absolute LabVIEW File Paths

[Soundar]

Hi,

I'm facing issue in creating the TestStand build using Absolute Path for LabVIEW Files and supported DLLs.

The LabVIEW project contains files in absolute path

C:\My App\Project\Program\LV File1.vi

C:\My App\Project\Program\LV File2.vi 

C:\My App\Project\Program\LV Control.ctl (dependent for LV File1.vi)

C:\My App\Project\Data\Support.dll (LV File1.vi requires it)

C:\My App\Sequence\My App.seq 

In the TestStand WorkSpace, I added C:\My App folder completely and configured the deployment settings for the destination location to C:\My App (Windows Drive and folder 'My App').

But when I create build, the ctl files and DLL files are placed inside one 'My App' folder. (Only dependent ctl files and dependent DLL files are not installing in desired folder)

The Target looks like..

C:\My App\Project\Program\LV File1.vi

C:\My App\Project\Program\LV File2.vi 

C:\My App\My App\Project\Program\LV Control.ctl (dependent for LV File1.vi)

C:\My App\My App\Project\Data\Support.dll (LV File1.vi requires it)

C:\My App\Sequence\My App.seq

Environment: LabVIEW 8.5.1 and TestStand 4.0.1

How can I solve this? 

Message Edited by Soundar on 10-06-2008 02:28 AM

[j_v]

I have the same problem.  Did somebody found in the meantime a solution?

In the "Installer Options" tab of the TestStand Deployment utility you can set the "Default Installation Subdirectory:" field.  It seems that this can not be empty.  Does somebody knows a workaround?

Kind regards,

Johannes

[Al.B]

Hi j_v and Johannes,

Are you still facing this problem, or were you able to find a solution?  I apologize that there were no replies to this forum when it was posted, and I wanted to check if you were still having problems.  If you are having any issues, I'd be happy to help, so let me know!

[RayFarmer]

Hi,

In the Deployment Tool in the Distributed Files | View Destination make sure the path you expect the ctl and dll are correct in the Installation Destination Subdirectory: control,

eg select the ctl and make sure the path is the same as the LLB of the VI's that use it. similar for the dll.

regards

ray farmer