Open alan-copeland-keysight opened 8 months ago
This could just be the user.lib / vi.lib locations - https://www.ni.com/docs/en-US/bundle/labview/page/specifying-the-location-of-shared-libraries-on-disk.html
This should be testable with customer supplied example .lvproj?
Check to see what must be done to make the dependency configuration to work. This may involve setting the path to where LabVIEW is looking for .vi's (possibly set to LabVIEW install dir?). This might be dependent on how user's store their .vi's, so this path may need to be stored as a Component Setting for the plugin? This path information might also be stored in the embedded LabVIEW resource.