Package Configuration Editor

VIPM 1.1 introduces a new concept of package configuration files. Package configurations are by far the biggest addition to VIPM. You can now save the state of your system in a file. This file contains all the information about which packages are installed for the selected LabVIEW version. At any time you can restore your system state by applying a configuration. Applying a configuration performs an installation of all the packages specified in the configuration file. Other features related to package configurations:

• VIPM can scan your existing LabVIEW source code project and find all packages in-use by that project. From the package configuration editor select Tools>Scan Project for Package Dependencies. This will bring up a file dialog where you can browse to a top-level VI or a folder of VIs to use as the basis of your scan. After the scan is complete you will be presented with a results list in a Package Action Confirmation Window.

Note 1: VIPM does not currently support LabVIEW *.lvproj files.
Note 2: In order for VIPM to determine the required packages, they must already be installed on your selected LabVIEW version.

• From the main VIPM window when you select one or more packages, from the menu you can select Package>Send to Configuration. This will add the selected packages to an existing opened configuration file or launch a new empty package configuration file.

• From the main VIPM window you can apply a configuration by selecting Tools>Package Configuration>Apply. This will open a dialog from where you can select an existing package configuration file to apply.

• When adding packages to the package configuration editor, VIPM automatically checks to see if the selected packages have required dependencies. If they have required dependencies, which are not selected, then VIPM will present a Package Action Confirmation Window which will list all the additional required dependencies.

• By default VIPM includes the packages inside the package configuration file. This allows easy distribution of your package configurations between computers that don’t have network access or if you just want internal package storage. You can toggle this feature on a per package basis by selecting the desired packages in the package configuration editor and from the menu select Package>Store Package in File on Save.

You can also change the default behavior of this feature for new package additions to the configuration. In the package configuration editor select Tools>Options>Store Packages in File When Adding.

Note: If packages are marked to be stored in the package configuration and they are not available locally (not cached), VIPM will attempt to download them automatically when you perform a save on the configuration file. This will cause the save process to take a little longer because VIPM has to download the package.

• You can perform a comparison of the contents of your package configuration to your existing installed packages. From the package configuration editor menu select Tools>Resolve Differences with Installed Packages. The results of the comparison will be displayed in the Package Action Confirmation Window.

• The following glyphs are introduced in the Package Configuration Editor:

Icon	State	Package is stored inside the configuration file?
	Package version is not compatible with selected LabVIEW version or operating system.	YES
	Package version is missing dependencies or there is a dependency conflict.	YES
	The package version listed is not the latest. There is a newer version available.	YES
	No Issues.	YES
No Icon	No Issues.	NO
	Package version is not compatible with selected LabVIEW version or operating system.	NO
	Package version is missing dependencies or there is a dependency conflict.	NO
	The package version listed is not the latest. There is a newer version available.	NO

Table 1 - Package Configuration Editor Glyphs