This series of documents covers how to create a VI package file using (VIPM) in order to facilitate the distribution of a third-party toolkit. The content and examples are taken for the most part from the VIPM Hands On document, with a few updates for the latest version of VIPM. That document uses an example math library to build a package, which we will use throughout the series to illustrate concepts. You can follow along by downloading the example or using your own library.
A VI Package is the file format (.vip) used for add-ons built by VIPM. You can think of a package as a smart zip file: the package contains all the VIs and resources for a specific LabVIEW add-on, as well as instructions that enable VIPM to install, remove, and manage the add-on automatically. Building and installing packages with VIPM is easier and more effective than using installers or zip files to distribute add-ons. Packages also allow you to specify your add-on's dependencies, simplifying installation for your users.
You can install VI Package Manager by clicking Find LabVIEW Add-ons in the LabVIEW Getting Started window or visit the JKI site at http://jki.net/vipm/download.
The following topics are covered in the VI Package Manager series:
For more information on VI Package Manager, please visit the group. For more information on creating toolkits and APIs, check out the Creating and Managing Reusable Code in LabVIEW document.
Why does VIPM takes too much of memory? I think it's necessary to optimize the memory in VIPM.
I'm using VIPM 2014.0.2(build 1976)
While we have adopted VI Package manager as the primary distribution tool for the LabVIEW Tools Network, it's actually a tool developed by the third part company JKI. I would recommend contacting them with any support issues or product recommendations at http://support.jki.net.
Thanks David_L. I have raised this to JKI support.