VI Package Manager is a program that enables you to discover, share, and create LabVIEW add-ons. You can work better by building reusable code libraries and tools for your developers and customers, manage LabVIEW add-ons used in multiple projects, and share reusable code libraries from your own private or public server.
v2013.0 [Oct 30, 2013]
Package Repository Manager
- Added the ability to switch between repositories from within the VI Repository Manager window. You can now switch between multiple repositories without exiting the VI Repository Manager window.
- Packages in the tree are now grouped by product name instead of package filename.
- You can now publish packages by dragging a VIPC file into the repository manager window or selecting it on disk. The packages contained in the VIPC will be published to the repository.
- An overlay glyph is shown on the folder in the tree if any package in the folder has been deprecated.
- Added the ability to collapse all or expand all tree items with buttons below the tree.
- The repository manager window is now non-modal and can be left open while interacting with other VIPM windows.
- You can now drag packages from the main VIPM main package list into the VI repository manager in order to publish them.
- You can now create a new repository from within the repository manager window.
VI Package Builder
- The Post-Build custom action VI now executes even if package building fails. An error indication is passed into Post-Build VI so you can selectively do work based on the error.
- VIPM warns you if you have not applied the VIPC before package building. The dialog has been changed to allow you to skip applying the VIPC if you choose.
- Changed behavior of the right-click menu 'Autogenerate Palette' on palette root icon. Now the action only rebuilds the palette while leaving the root icon untouched.
- There is now a separate dedicated page for the product description. This allows more room for editing. We've also added some formatting tips at the bottom to show what formatting is supported by VIPM.
- Previously, VIPM would show errors and display missing VIs when your packaged code was calling VIs from the RT or FPGA palette. This has been fixed and VIPM will not report these VIs as missing. In order to successfully complete the package building process you must wrap sections of your code which call RT or FPGA specific VIs within a conditional disable structure.
- License files (*.lf) are now visible in the source files tree and can be managed just like other support files. This is useful for people that want to do their own custom license binding.
- If you have specified custom pre and post build actions using VIPM Pro and try to execute the same build spec in VIPM Free, VIPM now brings up a warning (which can be ignored) instead of skipping the actions silently.
- If you have specified dynamic license binding using VIPM Pro and try to execute the same build in VIPM Free, VIPM now brings up a warning instead of ignoring the dynamic license binding silently.
- An enhancement was added to palette editor. Tip strips were added to the VI Icons in the palette editor. When you hover over the icon, VIPM displays the actual VI name from your source folder.
- An enhancement was added to the IDNet driver import wizard. Now VIPM asks you to choose the LabVIEW version you would like to use for importing the driver instead of using the lowest compatible version be default.
- An additional enhancement was added to palette editor. Now there is a checkbox on the palette editor page called: "Apply Short Names to VI Titles" which is off by default. When enabled, it takes the short names assigned to the VI icons and writes this to all the VI titles by default. This action applies to the packaged code. The source remains untouched. Individual palette icon short names and title overrides are respected.
General
- You can now create empty VIPC files (VI package configurations) with no packages. These can be used as placeholders in projects or for whatever other purpose.
- VIPM now automatically executes a LabVIEW menu refresh command when installing packages on LabVIEW 2013 and greater.
- A menu item was added to the Help called: "Save Troubleshooting File for JKI Support". This will automatically gather internal error logs and system information and save them to a file which can then be sent to JKI support staff to help solve problems with VIPM.
VIPM Installer
- The VIPM installer now embeds the necessary LabVIEW run-time engine with it. This makes installation even easier.
- The VIPM installer can now be run silently from the command line for automated installations.
- VIPM now adds itself to the firewall exception list automatically during install. This resolves some instances where VIPM cannot connect to LabVIEW.
Bug Fixes
- Package Installation - If a package contained a post-uninstall custom action and the action generated an error, it would leave the installed package in a state where it could not be uninstalled, or reinstalled. This is now fixed.
- VI Package Builder - 'Show in Explorer' from build complete dialog. Clicking on the 'show in explorer' button would not function as expected (fixed).
