What's New in VIPM 3.0
VIPM 3.0 is a major release that introduces package sharing over the network, via the new VI Package Repository feature available in VIPM Enterprise. This feature enables effective code reuse for teams of developers, allowing them to find new packages shared by other team members from within VIPM.
Mac and Linux Users: VIPM 3.0 is currently only available for Windows. Releases for Mac and Linux are on the roadmap, but we do not have an estimated availability date at this time.
- During the installation process, you may see a dialog stating that VIPM's installed files (cache, installation database, etc.) are being migrated to a new location. Depending on the size of your cache and installation database, this process might take a few minutes (but probably much less). This migration is necessary for supporting Windows Vista.
New and Changed Features
- Support for Windows Vista -Several improvements were made to allow full support for Windows Vista.
- Resolve Missing Dependencies - The VIPM Main UI now shows missing dependencies and allows easily resolving dependencies (just as the PCE window does already)
- Performance Improvements - Faster installation and use of VI Packages and VI Package Configurations. Faster Check for Package Updates. Faster startup time for new VIPM users
- Improved Package Conflict Detection - Package conflicts are now used by dependency resolver. Conflicts are displayed as required to be uninstalled.
- Drag and drop support of files onto VIPM Main UI - Users can now drag and drop *.ogp, *.vip, and *.vipc files onto the VI Package Manager UI.
- Drag and drop support of VIPC files onto VIPCE UI - Users can now Drag & Drop *.vipc files onto the PCE window to open them for editing.
- Build Hook VI Path Improvements - several improvements:
- Support for pathroots (or symbolic paths) in Build Hook VI paths, which allows creating a package of build hooks that are shared by multiple VI Package build specifications.
- Build Hook VI paths now display as relative paths (relative to the VI Package Source Folder) instead of absolute paths.
- All build hook parameters are passed to both pre and post build hooks.
- New parameters added:
- Package Source Folder (path) - The absolute path of the VI Package Source Folder.
- Package Member Source Files (array of paths) - A 1D array of (absolute) paths of the package member source files.
- Package Version (string) - The version number (e.g. "2.1.3") of the package
- Package Name (string) - The name of the package (e.g. "company_lib_array")
- Package LabVIEW Version (string) - The name of the LabVIEW version (e.g. "9.0")
- Network Package Sharing - VIPM Clients can connect to a centralized VI Package Repository
- Team-based code reuse - VIPM Enterprise can publish VI Packages to centralized VI Package Repository for team-based code reuse
- User Management -control which users are authorized to access the VI Package Repository
- Deprecate Packages - discourages use of outdated packages by hiding them from users
- MD5 Checksum Validation of VI Packages - allows users to know if they have the officially released version of a package (or a different package that has the same name and version)
- 1437: Failed uninistall leaves package in uninstallable state
VIPM is now smarter about handling failed uninstalls more gracefully
- 5594: "File > Add Package(s) to Package List " fails for many files at once
When adding many packages at once, VIPM now shows a dialog listing the first 10 packages and a description of what will happen next if the user chooses to install the packages.
- 5651: PCE should display read-only status.
When a read-only VIPC file is opened, the text "(Read Only)" is shown after the file name and the user is prompted to save a copy of the file, when the save action is selected.
- 5708: VIPM scrollbars can become hidden until package list change
VIPM scrollbars correctly show and hide when VIPM window is resized.
- 5742: When Scanning for Dependencies from VIPB, the PCE window does not close on exceptions
The VI Package Configuration window now closes (after the error message is shown) if any exception occurs during project scanning from within VIPB window.
- 6005: Scanning a project with no dependencies causes no package action suggestions
When no dependencies are found, the action confirmation dialog will be presented, if non-dependency packages need to be removed.
- 6335: Dependency versions not updated when vipc file is updated due to scan
VIPB package dependency versions are now slaved to the package versions in the VI Package Configuration (.vipc) file. Users cannot change the version field (since it must always equal the value in the VIPC file), which is now an indicator (rather than a control). The comparison ring now shows only ">=" and "=" options. Any VI Package dependency that uses an obsoleted comparison setting (">", "<", or "<=") will be silently converted to the new default setting: ">=".
- 6524: VIPM should delete package script VIs in temp folder even if read-only
VIPM now correctly deletes package script VIs in temp folder, even if they are marked as read-only.
- 6525: VIPM does not uninstall files that are read-only
VIPM now correctly uninstalls (deletes) read-only files that were installed by VIPM.
- 6537: Make Description field bigger in VIPB Advanced Build Parameters dialog
VI Package "Description" field (in the Advanced Build Parameters dialog) was made larger (vertically) to accommodate more visible text.
- 6560: Packages with hyphen in name can cause Select All to not select all packages
Select All now works as it should, in the situation where multiple packages share the same name, up to a hyphen character.
- 6594: When Scanning for Dependencies from VIPB, the PCE window does not close when no dependencies
The PCE window now closes when no dependencies found, if Scanning for Dependencies from VIPB.
- 6624: Column sorting in package lists should be case insensitive
Column sorting is now case insensitive.
- 7443: Newer packages can cause older packages to disappear from package lists of older LabVIEW versions
Packages compatible with older LabVIEW versions are now correctly shown, regardless of newer packages that are only compatible with newer LabVIEW versions.
- 7994: Using more than one double underscore ("__") in a VI Package's namespace suffix can cause the package's palette to be empty
Using a double underscore ("__") in a VI Package's namespace suffix now works without issues.
Release Date: October 2nd, 2009