JKI Blog

Secrets of the VIPC: Pinning Packages

Dec 5, 2014 1:45:33 PM Published by Jim Kring Leave a comment

A while back we wrote about the Secrets of the VI Package Configuration (*.vipc) file, which is used by VIPM to keep track of which packages are used in your LabVIEW projects.

2014-12-05_13-41-54

This makes VIPC files great for:

  • People who switch between multiple projects, or come back to old projects once in a while to fix bugs or add features.
  • People who work on the same project(s) on multiple computers.
  • People who hand-off projects to other developers for maintenance.

To create a VIPC file, VIPM scans your LabVIEW projects to automatically find package dependencies. However, sometimes you need to manually add a package that VIPM can't find, or perhaps you're using a packaged development/build tool that's not really part of your source code.

In these cases, where packages have been manually added, you probably don't want VIPM to suggest removing the package after doing a Scan Project to find package dependencies. That's where "Pinning" a package comes in very handy.

“Pinning” a package prevents VIPM from removing the package after a Scan Project, if the package is not found as a dependency. To pin a package, right-click on the package in the VIPC window and chose Pin Package (note: if it has a checkmark next to it, it's already pinned).

It's that easy!

For more useful information about VI Package Configurations, see our article How to use VI Package Configurations (VIPC).

Tags: code reuse, configuration, LabVIEW, pro, VIPC, VIPM

Subscribe to Email Updates

Posts by Topic

see all