Choosing a TestStand Deployment Utility Deployment Build Output
- Updated2024-11-26
- 3 minute(s) read
Choosing a TestStand Deployment Utility Deployment Build Output
Familiarize yourself with the different output types before using this help topic:
- Creating a deployable image
- Building an Installer with the TestStand Deployment Utility
- Building a package distribution with the TestStand deployment utility
Feature Comparison for TestStand
Deployment Utility build output types
| Feature | Deployable Image Only | MSI Based Installer | Package Based Distribution - Single Package | Package Based Distribution - Repository | Package Based Distribution - Package Installer |
|---|---|---|---|---|---|
| Consolidates all files in the deployment into a single file | - | - | Yes | Yes | Yes |
| Can be installed by running a single application | - | Yes | Yes | No | Yes |
| Deploy files to multiple destinations on a test station computer | - | Yes | Yes* | Yes* | Yes* |
| Allow the user to specify a custom target directory for files while installing the deployment on a test station computer | Yes | Yes | - | - | - |
| Allows registration of executables or DLL as activeX servers on the test station computer | - | Yes | - | - | - |
| Allows creation of program items in the start menu for files in the deployment | - | Yes | - | - | - |
| Allows creation of shortcuts to files in the deployment | - | Yes | Yes, with restrictions¹ | Yes, with restrictions¹ | Yes, with restrictions¹ |
| Automatically import hardware settings using a MAX configuration | - | Yes | - | Yes, with restrictions² | Yes, with restrictions² |
| Include custom commands to run 3rd party tools or executables | - | Yes | - | - | - |
| Create a file association for TestStand sequence files to a specific User Interface application | - | Yes | - | - | - |
| Available in 32-bit and 64-bit TestStand | Yes | Yes | Yes | Yes | Yes |
| Supports installation with no user interaction (silent installation) | - | Yes | Yes | Yes | Yes |
| Can be installed on a clean machine without NI software | Yes | Yes | No, NI Package Management software and required drivers must be present | No, NI Package Management software must be present | Yes |
| Includes required drivers and run-times in the distribution | - | Yes | No, dependencies are referenced only | Yes | Yes |
| Require a specific version or version range for required drivers and components | - | No, but included drivers will be installed if an older version is present on the deployment target | Yes | Yes | Yes |
| Include references to recommended or optional drivers or components | - | - | Yes | Yes | Yes |
| Create patch distributions which contain only new or updated files | - | Yes | - | - | - |
| Create patch distributions which contain only new or updated drivers and components | - | Yes | Yes | Yes | Yes |
| Include MSI-based additional components | - | Yes | - | - | - |
| Include package-based additional components | - | Yes, but only automatically detected dependencies | Yes | Yes | Yes |
| Distribute deployment with NI package distribution tools | - | - | Yes | Yes | Yes |
¹Shortcuts in package deployments do not support the command line arguments and start in options
²MAX configuration imports from package based distributions do not support silent installation
Choosing the Best Build Output for Your Deployment Scenario
If multiple deployment output types are viable based on the table above, consider the below recommendations to choose the best option for your requirements.
- The deployment requires specific software versions of drivers and components to meet validation requirements. Recommendation: Create a package based deployment and configure the package dependencies to require a specific version of all drivers. Create a package installer or repository to include the required versions of the dependencies in the software.
- The deployment will be installed on many test station computers with network access, and each must have the same version of driver and components. Recommendation: Use the repository build output to generate a feed which references all required drivers. Host the feed and packages in a network location where it is accessible by the test station computers. Use package management software to register the feed on the test station computer to access the packages.
- The deployment will be installed on many test station computers without network access, and each must have the same version of driver and components.Recommendation: Create an MSI-based installer with all required software, and ensure that test station computers do not have any NI software present before installing the deployment.