Note: Other release notes can be found here.
What's New in VIPM 2014.0.1 (build 1967)
New Features and Fixes
16227 - There is an error in VIPM during the display of the package dependencies. In some situations, VIPM reports a dependency conflict when one should not exist. This manifests as exclamation marks (warning) symbol on the package list in the main menu. It also prevent the installation of the package that has the dependency conflict. This has now been resolved.
16059 - License agreement path gets wrong relative path after vipb save. If you specify a license agreement and then save the package build spec. Next time you open the package build spec, the path would be wrong to the license agreement. This has now been fixed.
16060 - When clearing licence activation file or license library fields, no dirty dot shows in title bar. This is a minor cosmetic issue that may cause confusion when clearing of those fields. This has now been fixed.
Cases 15894,15965,15974 - Error 7 when building package with class targeted to LLB. - This is related to the "Add palette to class" feature in package building. When setting a class palette for classes inside of an LLB. Sometime you would get error 7 during package building. This has been resolved. There are several other issues resolved related to this VIPM feature. If you are using the "Add palette to class" feature in package building then it's highly recommended to upgrade to this version.
Case 15964 Password protection on folders causes folder to be installed at wrong location. - This is a package building issue. Under certain conditions, if you specified password protection on a subfolder of VIs. This would cause that subfolder to install to the wrong location during installation.
- Improved installation on Windows 8 (sometimes installer would hang or freeze in the middle of installation).
- Packages built with VIPM 2014 can only be installed on VIPM 2014 or newer. Package built with VIPM 2014 cannot be installed on versions of VIPM 2013 or older. Details.
- 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.