03-21-2017 02:38 AM
If any code modules DLL called in NI test stand steps, It can be searched using absolute path or relative path, When it is deployed.
Some times both options Don't search the dll and says 'file not found' due to the change in the installation directory folder structure.
During the building of the deployment, If it is possible to add the list of items present in the "Search Directory" to the Deployment package, and During the installation, those items should get added to the list of items present in the "Search Directory" of the target machine.
Solved! Go to Solution.
03-22-2017 01:18 AM
You can setup destination location of the files, during deployment - simply by changing target folder name (when you change view to "View Build Preview", you have active filed "Installation Destination Subdirectory" in the right tabe "File Properties, and also selector of default directories "Installation Destinations"). So by this, you can force deployment to put dependencies to the folder with proper structure, and you make sure, that all dependencies files are distributed together with build.
So, you can add you files to TestStand Directory, which is by default in Search Directories list, I guess; and then while putting files to target machine, those files will be already in the Search Directories list. You can give it a try, and see whether it'll help...
Thanks a lot,
03-22-2017 09:23 AM
Search directories are stored in a configuration file. If you include that file in your deployment, it will copy over the search directories.
Including TestStand Configuration Files in a Deployment
For TestStand 2014 SP1 and earlier, it is TestExec.ini. For 2016 and later it is SearchDirectories.cfg.
Hope this helps!
Trent