This page contains the latest builds of VIPM which are not available from the general download page. The purpose of these versions is to respond quickly to bug fixes or small feature enhancements without exposing the general user population. The versions listed below are stable but may contain enhancements or features that may be modified or removed in the final public build. You should only download and use these builds if the issue listed affects you or you have been instructed to do so from JKI support.
If you are looking for the latest general public release, click here.
Windows: VIPM 2014.0.0.1963
- 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.
- 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.
- 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.