Can I Build Labview Tools into a Package Using Vi Package Manager? Can This Include Third Party Tools?

Updated Jan 18, 2019

Reported In

Software

  • JKI VI Package Manager
  • LabVIEW

Issue Details

If you are using tools from the LabVIEW tools network, can they be built into a package in the VI package manager?  If so, is it only NI developed tools on the tools network, or can 3rd party tools be included as well? 

Solution

Yes they be built into a package in the VI package manager.

It is not limited to only NI developed tools on the tools network. 

Additional Information

The LabVIEW Tools Network has a repository of packages that you can connect to from your desktop to download add-ons directly into LabVIEW or get updates for packages you already have installed. In terms of quality assurance, all third-party products on the LabVIEW Tools Network repository (which VIPM connects to automatically) are tested as part of the Compatible With LabVIEW program. 
 
In addition, for developers who create paid add-ons, VIPM also integrates fully with the third-party licensing/activation feature in LabVIEW. This gives developers the ability to protect their intellectual property and offer free 7-day evaluations of their software.
 
Note that VIPM was not built as a replacement for building an EXE installer. For deploying LabVIEW EXEs or stand-alone products, you still want to build a traditional MSI installer using the LabVIEW Application Builder or another installer technology. Rather, VIPM’s optimal function is really for code reuse scenarios, whether that’s sharing add-ons that are VI-based APIs (that is, the “palette” use-case), or part of a software engineering process.  For advanced package management functionality, such as configuration management or managing code repositories within an organization, JKI offers Professional and Enterprise versions of the product

WAS THIS ARTICLE HELPFUL?

Not Helpful