LabVIEW should tell me what toolkits, modules, and drivers are required for a VI

[pjtanz]

I distribuute a lot of code, and sometimes it's difficult to tell my users what they need to install in order to run that code.  It would be nice if I (or a user) could run a built in LabVIEW utility that tells me what a given VI needs to run.

For example, do I need DAQmx, Mathscript, Robotics?

[smercurio_fc]

If you're the developer shouldn't you know what you need, by definition? Are you creating installers? This allow you to include the required installers.

[AristosQueue (NI)]

But, smercurio_fc, what if I'm not the developer? What if I am given a VI and it is broken because subVIs are missing? That happens to me all the time with VIs attached to bug reports. I can see the value in a feature like this.

[Mads]

I would like this feature in the application builder's "Additional Installers" section.

Even if you are the developer it is difficult to always know when a requirement kicks in. Does the math in the code I wrote two years ago require the math kernel libraries? Or how about the locked VI that I got from the net? If the application builder could select the modules that are needed, and only those, then I would not need to uncheck things like NI Logos all the time, nor would I forget to include the NI-VISA RunTime.

(This auto-selection could be ON by default, but should be possible to turn off if you happened to want an additional module for other reasons.)

[RayFarmer]

I agree with Aristos, the number of times I've clicked open a VI only to find its broken because something is missing. So I can see this could be very useful.

[ChrisReed]

I have to agree with this idea, since we just came across a situation when trying to build an executable with VI's from the NI Report Generation Palette.  Little did I know (until I searched on the NI Forums) that I had to manually add two folders from vi.lib (LVClass & NIReport.llb).

[David S.]

Nice idea. I completely agree.

[SimonH]

Does VI Analyzer count as a built in tool?  Along with hundreds of other tests, it can check for NI Toolkit and Driver usage:

It doesn't cover modules yet but it may help some people who have this need today.

[chembloke]

Not just identify which modules are required to make a project work, but also provide links to download the modules/packages installers.

Better yet provide a package manager like the Linux distributions use so I can engage in one stop shopping

[Olivioloyer]

Totally Agree, it is a needed feature, and apparently still not implemented in LabVIEW 2013

[TomOrr0W]

I believe NI has implemented this with the Load and Save Warning List since the last comment was made.

See the discussion on https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Auto-detect-and-install-required-add-on-software-auto...