Skip to main content

VIPM 2016.0.0 Release Notes

VIPM Support
Updated

Note: Other release notes can be found here.

What's New in VIPM 2016.0.0

VIPM 2016 is a major release for for Windows that adds performance improvements and fixes some bugs. It is recommended that all VIPM users on for Windows upgrade.

Note: You will need an active VIPM Pro subscription in order activate VIPM 2016 into Pro Edition.

2016-05-17_09-28-14.png

New Features

  • Various Performance Improvements - Users can expect noticeable performance improvements, especially on multi-core machines, during launch, check network for packages, search box results while typing, and package list sorting by column.

Compatibility Note

  • Packages built with VIPM 2016 can only be installed on VIPM 2014 or newer. Package built with VIPM 2016 cannot be installed on versions of VIPM 2013 or older. Details.

Bug Fixes

  • 16733: Specifying package installation requirement of LabVIEW 32-bit or 64-bit was resulting in packages that could be installed on any LabVIEW bitness. Packages now specify the correct LabVIEW bitness requirement and are only installable on the specified LabVIEW bitness.

  • 16809: Source Only VIs were not being mass compiled during installation. Now, VIPM will force a mass compile in the target LabVIEW version, even when LabVIEW would otherwise not notify users of unsaved changes (e.g. a “dirty dot” asterix).

  • 17093: Repository Manager UI sometimes showed packages in wrong folders of tree-view. This now works correctly.

  • 17173: OS bitness showed up twice in package info dialog text (cosmetic bug). This now shows correctly.

  • 17175: Password manager not working with HTTPS (SSL) package repositories. Username and passwords are now correctly stored and recalled for HTTPS (SSL) package repositories.

  • 17196: Some non-system packages were being shown when switched to System target.

Known Issues

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

Related articles

Comments

0 comments

Article is closed for comments.