How do I configure teststand search directories

[Steve_Block]

   I have two teststand projects that have similar structures because I created one by copying the other. The problem is that the files with identical names are linking to each other instead of a path relative to where the sequence file is stored. How to I configure the search directories to be sequence file dependent instead of global to the station?

[j_dodek]

Hi Steve,

Figure out this example

Just copy the dll to C:\ before testing

Greetings

juergen

[S_Hong]

Hi Steve,

Another solution to this problem may be to simply ensure that any code modules you are calling in your sequence file are being called via relative paths and NOT absolute paths. Also, make sure to have your sequence file directory as the top search directory under Configure » Search Directories.

I hope this helps.

[Steve_Block]

That's what I want. For everything to be relative. I put my sequence files in a different directory as my code files and finally figured out that I needed to use a ..\\code\\file.vi convention to reference every file.

[Mark_Ireton]

That is a good trick.  

I had always assumed that TestStand was storing the relative path information, thinking that the path was relative to the sequence file directory.  But it seems that "relative" means relative to the search directories because I find that unless I specify the path as you did, TestStand will traverse the search directories to find the file, even though neither the sequence file or the module file has moved.

I found that when the Module tab of the Step Settings window is open, the Sequence Editor continually opens the file, which means that it is continually traversing the search directories if a relative path is used. In my case that can cause a lot of disk churn for files outside of my sequence file directory because of a large number of "common" directories and files that are shared amongst many projects.  I will work on tuning my search directories to alleviate that problem.