VI Package Manager

Publish Date: Aug 07, 2013 | 25 Ratings | 3.04 out of 5 | Print | Submit your review

Table of Contents

Manage and Share Reusable VIs and Add-Ons

JKI Software’s VI Package Manager (VIPM) makes using and distributing an NI LabVIEW add-on simple.  With VIPM, it is easy to manage and share reusable VIs across multiple projects, computers, and teams of developers. The add-on simplifies the process of bundling your VIs and preparing them for distribution.

A VI package is a single file that is handled automatically by VIPM. This makes sharing LabVIEW code easy with the following added benefits:

  • Installs the package into LabVIEW seamlessly
  • Handles different versions of LabVIEW with the same package (no need to rebuild)
  • Works with multiple OSs (Windows, Mac, and Linux)
  • Helps you reduce project costs by implementing a code reuse process in your organization
  • Automatically mass compiles your VIs into the version of LabVIEW you are installing the packages into
  • Notifies, downloads, and solves the dependencies for you if a package requires dependencies
  • Helps you get started and directs you to examples and help when a new package is installed

Figure 1. VIPM helps you manage the add-ons you have and install new ones.

Download Add-Ons Directly Into LabVIEW

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.

Additional Resources

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit