I'm trying to deploy TestStand sequences to many test stations. On my dev machine everything works fine. My system consists of an exe for the TestStand UI, a couple of PPL's for the guts of the application, and of course the run time engines for both TestStand and LabVIEW. I've tested the PPL's, UI, and .seq on the dev machine and all works fine. When I deploy to my test station computer, I get errors that vi's are broken or are unable to load required files.
Some remote debug shows that the files not loading are DLL's that are called from the PPL's. In the PPL creation, the DLL is located in the same directory as the PPL. If I drop my TestStand UI exe into the same folder as one of the PPL's, everything from that PPL loads fine (including the DLL). Search paths include the Top Level vi directory, so this makes sense. However, it still won't load the other DLL, referenced in a different directory by the other PPL. The PPL's are loaded with an absolute path, but the DLL's are relative from within vi's inside the PPL.
I tried adding the parent directory to the TestStand search paths (I created a new TestStand deployment with the Cfg files, then installed it on the deployment machine). Same issue.
Is this an issue with LabVIEW Runtime search paths?
How do I ensure these directories are part of the search paths for TestStand and LabVIEW Runtime?