Thinking in G

I'm happy to announce that JKI has shipped the 1.1 release of VI Package Manager , a tool that makes it simple to find, download, and install reusable LabVIEW VIs directly into the functions palette. We're very proud of this release, as it adds an important new feature: configuration management.

In this release, we've added a new construct called a VI Package Configuration file, which allows you to save and recall the state of LabVIEW for each of your projects (meaning, which libraries are installed).
And, we've even added support for saving the actual package files inside a VI Package Configuration file, so that you can easily store the packages inside your project folder (and thus use your source code control system to make the packages available to other developers and computers).


Configuration management was a very important problem for us to solve, since we work on a lot of different LabVIEW projects, both internally at JKI and for our clients. We can't afford the risk of not knowing which versions OpenG and other library VIs are required for a given project. So, before we start working on a project, we use VI Package Manager to apply our project's VI Package Configuration file.