Mode Tab

Use the Mode tab to create a full deployment or a patch deployment and to specify related settings for each type of deployment.

The Mode tab contains the following options:

• Deployment Version —Indicates the software version number to use to identify the deployment. The deployment utility auto increments the version by default each time you update the deployment.
  • MSI-based installers —The version number has the format X.X.X . After a successful build, the third number in the version increments. If you enable the Lock to Deployment Version option on the Advanced Installer Options dialog box, the Version option on the Mode tab also determines the installer version number.
  • Package-based installers —The version number has the format X.X.X.X . After a successful build, the fourth number in the version increments. If you enable the Lock to Deployment Version option on the Configure Package Options dialog box, the Version option on the Mode tab determines the package version number.
• Output type —Select one of the following build outputs. Refer to the Choosing a Build Output topic for more information about how to select the best setting for your application.
  • Deployable Image Only —The deployment files are moved to the specified image directory on the System Source tab.
  • MSI-Based Installer —In addition to the deployable image, the deployment utility creates an installer to distribute the system. When you select this option, the Installer tab is enabled, which you can use to configure the installer.
  • Package-Based Distribution —In addition to the deployable image, the deployment utility creates a package distribution. When you select this option, the Package Distribution Options tab is enabled, which you can use to configure the package distribution. You can configure the package output type using the options below:
    • Single Package —The files in the image directory are packaged into a single .nipkg file. Dependencies you select are referenced by the package, and must be installed on the deployment target to install the package.
    • Repository —In addition to the main package, all dependent packages are also included in the deployment (the repository). A feed is generated which references all included packages in the repository. To install the deployment, you can register the feed in NI Package Manager on the target machine.
    • Package Installer —In addition to the main package, all dependent packages are also included in the deployment. A standalone installer is generated which installs all the packages on a machine. The installer will also install NI Package Manager if it is not present on the machine.
• Create new Full Deployment —Creates a new full deployment that contains all the files in the test system.
• Create new Patch Deployment —Creates a new patch deployment that contains only the subset of files that have changed since the previous full or dependency patch deployment . This option is available only when you have previously created a full deployment.
  Note (32-bit TestStand) You must use the 32-bit TestStand Deployment Utility to create a patch for a 32-bit full deployment. (64-bit TestStand) You must use the 64-bit TestStand Deployment Utility to create a patch for a 64-bit full deployment. Create a new full deployment to update a 32-bit test system to a 64-bit test system.
• Depend on previous Full Deployment —Creates a patch deployment based on the previous full deployment.
• Depend on previous Baseline Patch Deployment —Creates a patch deployment based on the previous baseline patch deployment . This option is available only when you have previously created a baseline patch deployment.
• Make Baseline Patch Deployment —Designates a patch deployment as a baseline patch deployment , which you can use to create dependency patch deployments that contain only the files that differ from the previous patch deployment version of the file. TestStand supports only one baseline patch deployment at a time, and you can create a baseline patch deployment only from the most recent patch deployment you created. You must designate a patch deployment as a baseline patch deployment before you create another patch deployment. If you create another baseline patch deployment, you can no longer depend on the previous baseline patch deployment. Creating a new deployment also erases data of previous patch deployments that you do not designate as baseline patch deployments. This option is available only when you have previously created a patch deployment.
• User Files to Include —Contains the following options to control which files to include in the patch deployment.
  Note This option is not available for package-based distributions. Patch deployments for path distributions always contain user files.
  • Modified Files —Includes new or modified files from the previous full or baseline patch deployment in the patch deployment. You might need to also include files you did not explicitly modify to ensure that all the included files execute correctly. When you select this option, the deployment utility creates a temporary full deployable image , compares the checksums of all the files in the temporary full deployable image to the checksums of all the files in the previous full deployable image to generate a list of modified files, and then deletes all but the modified files from the temporary full deployable image to create the patch deployable image.
  • None —Does not include any files from the previous full or baseline patch deployment in the patch deployment. Use this option to build a patch deployment installer that contains only updated drivers and components.
  • Manual Mode —Use this option to manually specify files to include, to include additional files, and to replace existing files in the patch deployment.
• Upgrades and Patches to Include —Contains the following options to control which updates and patches to deploy for National Instruments products in the patch deployment.
  Note This option is not available for package-based distributions. Patch deployments for patch distributions always update the TestStand runtime and drivers.
  • TestStand Runtime and Drivers —Includes all installed TestStand Runtime and National Instruments driver updates and patches that support redistribution.
  • TestStand Runtime —Includes all available TestStand Runtime updates and patches that support redistribution.
  • Drivers —Includes all available National Instruments driver updates and patches that support redistribution.
  • None —Does not include any TestStand Runtime or National Instruments driver updates or patches.
• Overview —Describes the User Files to Include option you select.

See Also

Creating Dependency Patch Deployments

Patching Deployments