Allen Hunsaker

More info genericized. In the project, the hierarchy looks like this 1/DCS 2/Methods 3/lvclass 4/methods 5/private 6/Script.vi - this is the VI that searches for the DLL that I can't seem to save with DLL location. 5/Execute.vi... this vi calls the Script .vi but is not in the private folder as shown 2/Test App 3/.dll is here Creating the packed library puts the dll in the build project root

Built a packed library where VIs had error in the library. "This VI uses a dependency that has changed. That change requires this VI to recompile. This VI is compiled into a Packed Project Library and cannot recompile by itself. You must rebuild the Packed Project Library to account for the changed dependency." The VI in question is part of a Class. When I attempt to load the VI from the LabVIEW project, it has to search for a required .dll. I can point to the .dll while searching, so I know it's there. But apparently not where it is expected (Thus the search). I have saved it once open, but the .dll is searched every time I open it anyway. Not experienced enough with oop as related to packed library (LVLIBP) to know how to fix this. since I'm pretty sure that's what the dependency issue is for the packed library. Any ideas?