LabVIEW file dependency on vendor driver

[lvrat]

When using vendor driver VIs to create the project/application, is it recomended to include the VIs provided by the vendor (only the ones that are getting used in the appliction) in the project folder structure?

As there are multiple different instruments and different zip/installer from vendors, how to make the application self sustained so that it can be easily distributed and deployed? If the vendor Vis are not located under instr.lib then the application starts looking for VIs and then give the dialog to select the path, how to avoid this?

Each instrument has its own application and its own project.

[550nm]

Hi lvrat,

      If you're building an EXE, the build-process will scoop-up the VI dependencies needed (linked to) - you shouldn't need to include any other VIs.  If the Vendor stuff uses DLLS, then LabVIEW may automatically include those too, though, when DLLs call DLLs you may have to include the DLLs manually.

If your code calls any VIs "dynamically", that is "by name", then those need to be included manually - unless there's a static ref to them somewhere in the hierarchy.

If you just want to build the minimum-yet-complete source hierarchy, try File\"save hierarchy to new location".  That will scoop-up all/only the dependencies your're actually linked to.

Cheers!