What's New in VIPM 2020.1
VIPM 2020.1 is a Maintenance Release with bug fixes -- see VIPM 2020 release notes.
It is recommended that all VIPM 2020 users upgrade.
Improvements in this Release
- Windows Installer Improvements
- 18748 - VIPM Installer was sometimes raising an error stating "no mapping between account names and security IDs" when invoking the task scheduler. This has been resolved.
- Windows Explorer Extensions Improvements
- 18725 - There is now an "Add to VIPM Library" right-click option for VI Packages in the Windows File Explorer (Shell)
- 18762 - Upgraded VI Package icons to 2020 theme.
- Command-Line API Improvements
- 18751 - VIPM now shows the VIPM Edition selection dialog when the VIPM API is used to call a Community or Pro feature and QUIET is set to FALSE.
- VIPM Sign-in Changes
- 18759 - VIPM no longer requires sign in when installing packages from VIPM Community Repository on vipm.io. This was causing issues for some users due to their Enterprise IT/Networking configuration. Also, VIPM Browser now recommends sign-in when installing/uninstalling packages, and allows users to "continue as a guest" without signing in.
- VI Package Builder Improvements
- 18755 - A modal status dialog was showing during the build, which prevented using theVI Package Builder toolbar (and prevented aborting the build, if needed). This dialog is no longer shown, allowing users to click the Abort button on the VI Package Builder toolbar during the build process.
- VI Package Configuration Improvements
- 18728 - Escape key now cancels/closes Apply VIPC confirmation dialog. This makes it more convenient to cancel the action of Applying a VIPC file that is double-clicked in Windows File Explorer.
Minor Patch Builds
2020.1.2348 (Windows)
- 18768 - Fixed issue where VIPM could switch to a different active LabVIEW version (if user is using multiple LabVIEW versions concurrently) while in the middle of an installation, package build, etc.
- 18769 - Improved opening of VIPM Main UI when busy with a synchronous task, if opened from another window or API call.
Comments
0 comments
Article is closed for comments.