This seems to be an issue with understanding how LabVIEW libraries work. It seems like a complicated problem, but I will try to explain it as best as possible.
We have an existing NI project for making a Veristand Custom Device. It's based on a project template. In short, they are very complex LabVIEW applications that have a strict way of building them to interface with Veristand. If you haven't gone down this path, I would not advise it.
As part of that project, we have made subVIs for performing various functions. Those VIs currently exist in the System Explorer folder in Veristand Project (other folders: Engine, Help, Shared, Utility). Some of these functions are ones that I would like to reuse in a LabVIEW GUI on windows. The issue is that when I add those subVIs to the BD, it must import them as a .lvlib because I see that it gets added to the dependency list? When I go to run the main VI in the GUI project, I get a deployment dialog that eventually fails due to Custom Device.lvlib error. (Error -1967362042, Unable to start service).
However, if I close the project and just open the VI and run it (no project open), it runs fine. Any insight as to what is going on here?
