Note: Other release notes can be found here.
What's New in VIPM 2013.0.0
VIPM 2013.0.0 is a major release that adds some features and bug fixes over the previous release. It is recommended that all VIPM users upgrade.
New Features and Changes
VI Package Repository Manager
- 14096: We've added a new 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.
- 14140: Packages in the tree are now grouped by product name instead of package filename.
- 7239: 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.
- 7243: An overlay glyph is shown on the folder in the tree if any package in the folder has been deprecated.
- 14090: We've added the ability to collapse all or expand all tree items with buttons below the tree.
- 14091: The repository manager window is now non-modal and can be left open while interacting with other VIPM windows.
- 14092: You can now drag packages from the main VIPM main package list into the VI repository manager in order to publish them.
- 14111: You can now create a new repository from within the repository manager window.
- VI package repository management is now available on the Mac OS X platform. Previously, repository management was disabled for Mac OS X due to certain cross-platform incompatibilities. These issues have been resolved and we're happy to release repository management on the Mac platform.
VI Package Builder
- 11365: 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.
- 14116: 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.
- 12996: We've 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.
- 12367: 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.
- 9971: 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.
- 14122: 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.
- 14175: 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.
- 14176: 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.
- 14164: An 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.
- 14429: An enhancement was added to palette editor. You can now add *.ctl (control) files to the functions palette. This allows you to add (for example) typedefs for dropping as constants on the diagram.
- VI package building is now available on the Mac OS X platform. Previously, package building was disabled for Mac OS X due to certain cross-platform incompatibilities. These issues have been resolved and we're happy to release package building on the Mac platform.
- 10519: 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.
- 14098: VIPM now automatically executes a LabVIEW menu refresh command when installing packages on LabVIEW 2013 and greater.
- 14119: 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.
- VI package configuration (VIPC) file creation is now available on the Mac OS X platform. Previously, VIPC creation and editing was disabled for Mac OS X due to certain cross-platform incompatibilities. These issues have been resolved and we're happy to release VIPC creation and editing on the Mac platform.
- 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.
- 13597: VIPM now adds itself to the Windows firewall exception list automatically during install. This resolves some instances where VIPM cannot connect to LabVIEW.
- For the Mac OS X platform, we have now eliminated the VIPM Installer. VIPM 2013 for the Mac is now distributed as a DMG package. This solves a long standing incompatibility with installing VIPM on Mac OS X.
- 13496: 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.
- 13863: VI Package Builder - 'Show in Explorer' from build complete dialog. Clicking on the 'show in explorer' button would not function as expected (fixed).
- 13804: VI Package Builder - Before package building and if license binding is enabled, VIPM now checks to see if you have correctly filled-in the licence and library fields correctly. It will display a warning message before building the package.
- 14066: VI Package Builder - If the package source contained and LVLIB that contained missing VIs on disk, then VIPM would abort the package build with an error 43. Now VIPM ignores missing VIs in LVLIBs and the package building completes normally.
- 14103: VI Package Builder - If the package source contained VIs which required activation and they were not activated. VIPM would generate an error 1507 during package build. Now VIPM verifies that all VIs are activated correctly and if not, displays a dialog with instructions on how to activate.
- 14124: VI Package Builder - If license binding was enabled and you decided to rename (prefix or suffix) the licensed LVLIB, then license binding would fail silently. Now VIPM supports renaming the licensed LVLIB (prefix or suffix) and correctly locates it. Also, VIPM now displays a message when it has a problem finding either the licensed library or the license file during build.
- 13858: VI Package Builder - If your package source contained an LVCLASS library inside an LLB, VIPM would display an incorrect error indicating that it could not determine the version of LabVIEW to use for the build. This has been fixed.
- 14136: VI Package Builder - In some instances, VIPM would report that some dependent VIs were missing during package building even though they were clearly available. This was due to VIs containing corrupt linker information. This has been fixed and VIPM now ignores the linker errors and continues to build correctly.
- 14153: VI Package Builder - If you opened up a VIPB file on a computer that did not have the Third Party Licensing and Activation toolkit installed, and you previously had Dynamic License binding enabled, VIPM would silently disable license binding without warning. Now, Dynamic License binding is left on and VIPM displays a message before a build is performed.
- 13976: VI Package Builder - If you had renaming enabled for a VI in the source files settings page (prefix-suffix), VIPM would not show you this name in the palette editor. Now VIPM correctly displays how the VI name will appear to the end user with the renaming applied.
- 14127: VI Package Builder - When executing package building using the VIPM API, VIPM would sometimes display dialogs during the source validation step that required user interaction. Now these have been removed and instead, any error messages are returned through the API's error cluster.
- 14152: VI Package Builder - If any of the paths for the custom actions fields contained certain characters. VIPM would abort the build with a cryptic error message. This is now fixed.
- 14425: VI Package Builder - There was a certain situation where package building would fail if any of the packaged VIs were calling VIs inside of PPLs (packaged project libraries - lvlibp) which shipped with LabVIEW. For example, the NI icon editor API. This is now fixed.
- 14141: VI Package Repository Manager - When you right-clicked on a package in the tree, sometimes the right-click menu would not pop-up. This is fixed now.
- 14165: VI Package Repository Manager - Package building would fail if you had Dynamic License binding enabled (with an lvlib password) and you had also set a password on the lvlib in the source files settings page. Now VIPM displays an explanatory message and prevents building.
- 13996: VI Package Repository Manager - When initializing a new repository, you were prompted for folder location. If you click cancel, the repository manager window would still open. This has been fixed.
- 6628: VI Package Repository Manager - The repository RSS XML feed did not contain the correct formatting for apostrophes, which caused unformatted text to show up in the feed. This is fixed.
- 7464: VI Package Repository Manager - The repository RSS XML feed was not fully RSS compliant and would not work with some RSS readers. Fixes were made for the maximum compatibility.
- 14148: VI Package Repository Manager - Previously, it was possible to add packages to the repository that were corrupt or invalid. This would cause repository corruption. Now, VIPM prevents corrupt or invalid files from being added to the repository and displays a message indicating this.
- 8008: VI Package Configuration - VIPM would fail silently and not provide feedback to the user when scanning a project that contained VIs saved in a version of LabVIEW older than 4.0. Fixed. VIPM now reports and error.
- 14137: IDNet Driver Import Wizard - After the importing process, the lvproj file contents had broken members (Items missing on disk warnings). This is now fixed and project members now resolve correctly.
- 14160: Connecting to LabVIEW for the first time - There was an issue where VIPM would not connect to LabVIEW for package installation if LabVIEW was in evaluation mode. This has been resolved.
- 14089: VI Package Builder - In the VIPM palette editor, you can add VIs to the palettes that are installed in the Examples folder in LabVIEW. However, these VIs will not show up in the LabVIEW palettes when installed even though the VIs get installed correctly in the Examples folder. This is due to a limitation with NI's Palette editing API. We are working closely with NI to resolve the issue and hopefully will have a fix in a future release of VIPM.
- Update (9/20/2013): There is no plan currently from NI to fix the above issue.
- 14065: VI Package Builder - In the VIPM palette editor, you can add VI templates to the palettes. However, these VITs will not show up in the LabVIEW palettes when installed even though the VIs get installed correctly. This is due to a limitation with NI's Palette editing API. We are working closely with NI to resolve the issue and hopefully will have a fix in a future release of VIPM.
- Update (9/20/2013): There is no plan currently from NI to fix the above issue.
- 14178: VI Package Builder - This issue affects package building of classes and is reproducible in the LabVIEW development environment using source distributions. So it is not limited to VIPM. Dynamic dispatch of class members will break if both of the following conditions are true: a) You rename class members (prefix-suffix) in the VIPM source files settings page. b) you have a parent-child class hierarchy that is more than one level deep. We have reported this to NI and are hopeful it will be fixed in an upcoming LabVIEW release.
- Update: The issue above is fixed in LabVIEW 2013
- 13790: VI Package Builder - This issue affects package building of classes. The issue appears to be isolated to VIPM. It's possible to build a package where members of a friend class cannot access members of a community scoped class. This occurs if you set a password on the community scoped class in the VIPM source files settings page.