Configuring the Package Settings
- Updated2025-07-23
- 2 minute(s) read
Package distribution settings are configured on the package distribution options tab. On this tab, you can choose the package name and the destination where TestStand Deployment Utility will generate the distribution.
To configure additional settings for the package, click the Package Attributes button.
Note The Include Required Certificate Packages option determines whether to include certificates packages, which reduce the number of prompts you will receive when installing the package. This setting applies only to feeds and package installers.
To Include package-based dependencies, click the Dependencies button. For each dependency you select, you can configure the dependency level:
- Required (default)— The package cannot be installed unless the dependency is on the system or can be found by NI Package Manager through a registered feed. These packages will be included in the deployment in the repository or package distribution mode.
- Recommended— The package can be installed without these dependencies.They are not included in the repository or package distribution mode. If the dependency package is referenced in a feed on the test station computer, the dependency will be displayed as an optional package when the deployment package is installed, and will be selected by default.
- Optional— The same as a recommended package, except that optional packages are not selected by default when installing the deployment package.
You can also specify a required version range for each dependency:
- Any Version— Do not require a specific version.
- Specific Version— Require the exact version number specified in the Version control.
- Greater Than (default)— The required package version must be greater than the version specified in the Version control. The version field is set by default to the currently installed version of the package.
- Less Than— The required package version must be greater than the version specified in the Version control.
- In Range— The required package version must be in a specified version range. When you enable this option, a second version control is available to enter the maximum version.
The following features are currently not supported in package mode:
- Creating program items in the start menu
- Registering deployed files as an activeX server
- Executing Custom Commands
- Including readme files or license agreements
- Media spanning