Monolithic vs. Modular Software Reuse Libraries (Part I) »
« In Place Element Strucure – Saves Time and Prevents Bugs
VI Package Manager 1.1 Released

Posted on Tuesday 5 February 2008

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).

VI Package Configuration File

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.

Apply a VI Package Configuration


4 Comments for 'VI Package Manager 1.1 Released'

  1.  
    Yen
    February 5, 2008 | 10:33 am
     

    Congratulations, Jim.

    The previous versions of both Commander and VIPM were very good and this new feature sounds like it could be very useful for some things.

  2.  
    Jim Kring
    February 5, 2008 | 10:44 am
     

    Thanks, Yen. We hope you like it :)

  3.  
    Rajkumar
    April 30, 2009 | 12:09 pm
     

    Jim,

    I am really interested to know how you manage the dependencies of multiple version of the package.

  4.  
    Jim Kring
    April 30, 2009 | 9:16 pm
     

    Hi Raj,

    Each package defines its dependencies on other packages. And, each project maintains a list of the packages that it requires (depends on).

    -Jim

Leave a comment

(required)

(required)


Information for comment users
Line and paragraph breaks are implemented automatically. Your e-mail address is never displayed. Please consider what you're posting.

Use the buttons below to customise your comment.


RSS feed for comments on this post |

 

Bad Behavior has blocked 243 access attempts in the last 7 days.