Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

TestStand Deployment Utility

NI TestStand™ 2012 Help

Edition Date: August 2012

Part Number: 370052K-01

»View Product Info

Distributed Files Tab

Use the Distributed Files tab to view the list of files you specified to include in the deployment on the System Source tab, configure the installer destination location and settings for each file, and specify options for deploying LabVIEW files.

Note  This tab is not available when you disable the From TestStand Workspace File and From TestStand Public Directories options on the System Source tab.

The Distributed Files tab contains the following options:

  • Distributed Files—The files the system includes.
    Note Note  The string <SubVIs: Save to destination> as part of the item text in the Distributed Files list always denotes subVIs. You can change the location the subVIs are saved to using the SubVI Location option on the LabVIEW VI Options dialog box.
  • View—Specifies how the distributed files are displayed. You can display the files as they appear in their workspace, display the source of the files on the development system, or display the destination for the files on the test station computer.
  • File Properties—Contains the following options:
    • Source Path—The path of the selected file. This option is disabled when there is no file selected in the Distributed Files list.
    • Include without Processing Item or Dependencies—When you enable this option, the deployment utility copies a file to the deployment image directory without any additional processing during the build. The deployment utility does not attempt to find any dependencies of the file during analysis. You might use this option to deploy files that have already been processed, such as third-party step types that use LabVIEW VIs or the LabVIEW User Interface.

      You must ensure the LabVIEW Run-Time Engine can run the VIs for which you enable this option. The deployment utility does not attempt to determine if VIs with this setting are broken but does check for broken VIs in the image directory after copying the VIs to warn you if VIs you do not process break processed code modules.

      The deployment utility returns a warning if it includes a file in a deployment image directory as a dependency and you enabled the Include without Processing Item or Dependencies option for the file.
    • Include All Files in LabVIEW Project—When you enable this option, the deployment utility includes all the files in a LabVIEW project. By default, the deployment utility includes only the files steps in sequences call. This option is dimmed when you do not select a LabVIEW project in the Distributed Files control. When you select View Source from the View ring control on this tab, the files appear under the LabVIEW project to which they belong. When you select View Destination from the View ring control on this tab, you can select the destination for the LabVIEW project, which determines the destination for all the files in the project.
    • Installer Properties—Contains the following options:
      • Installation Destination—Specifies a directory Microsoft Windows or National Instruments defines on the test station computer, such as the Program Files directory or the <TestStand> directory, to which the deployment utility copies the selected files. You can select from several installation destination options. This option is dimmed when there is no file selected in the Distributed Files list.

        By default, the deployment utility installs files on the test station computer to the same location in which the file exists on the development computer. Use the Installation Destination option to install a file to a different location on the test station computer. For example, you can install custom configuration files for test station computer operators that are different from the configuration files test system developers use. You can save the custom configuration files for operators in a directory other than the default TestStand configuration directory on the development computer but install the files in the default TestStand configuration directory on the test station computer.
      • Installation Destination Subdirectory—A subdirectory under the installation destination. This option is dimmed when there is no file selected in the Distributed Files list.

        By default, the deployment utility installs files on the test station computer to the same location in which the file exists on the development computer. Use the Installation Destination Subdirectory option to install a file to a different location on the test station computer. For example, you can install custom configuration files for test station computer operators that are different from the configuration files test system developers use. You can save the custom configuration files for operators in a directory other than the default TestStand configuration directory on the development computer but install the files in the default TestStand configuration directory on the test station computer.
        Note Note  The deployment utility returns an error when a temporary path includes “.lvlibp”. You must disable the Output VIs to Packed Project Library option in the LabVIEW VI Options dialog box, change the Installation Destination option (and/or the Installation Destination Subdirectory option) on the Distributed Files tab of the TestStand Deployment Utility, enable the Output VIs to Packed Project Library option in the LabVIEW VI Options dialog box, and rebuild the deployment to resolve the error.
      • Register as ActiveX Server—When you enable this option, the installer you build with the deployment utility registers the file you select as an ActiveX Automation server. Register ActiveX server executables or DLLs so that client applications on the test station computer can find the files. This option is dimmed when there is no file selected in the Distributed Files list.
      • Create Program Item—When you enable this option, the deployment utility installer creates a Microsoft Windows Start menu item in the group that you specify in the Start Menu Item Group option on the Installer Options tab. For example, you can create a start menu item for a user interface. This option is dimmed when no file is selected in the Distributed Files list.
      • Force File to Install—Enabling this option overrides the default installer behavior and always overwrites existing files on the test station computer with the files the installer includes. For example, you can overwrite the existing TestExec.ini file on the test station computer with an updated version you include in the installer.

        Caution Caution  When you use this technique, an installer can replace a newer version of a file with an older version of a file, which can be problematic with DLLs because components on the computer might rely on functionality available only in the newer version of the DLL and might break when the installer downgrades the DLL. To avoid this issue, create a later version of the file with the changes you want and include the file in the installer you build with the deployment utility to overwrite only earlier versions of the file.


        This option is dimmed when you have not selected a file in the Distributed Files control.
      • Shortcuts—Launches the Shortcuts dialog box, in which you can specify shortcuts for the deployment utility installer to create in multiple directories for the file you select. For example, you can create a shortcut to a user interface on the desktop and in the start menu.
  • Analyze Source Files—Causes the deployment utility to analyze the workspace and files in the <TestStand Public>\Components, <TestStand Public>\CodeTemplates, and <TestStand Public>\UserInterfaces directories.
  • Expand All—Expands all items in the Distributed Files list.
  • Collapse All—Collapses all items in the Distributed Files list.
  • LabVIEW Options—Launches the LabVIEW VI Options dialog box, which contains options specific to LabVIEW VIs.

Refer to Chapter 7, Effectively Using LabVIEW with TestStand, of the Using LabVIEW and LabWindows/CVI with TestStand manual for more information about how to best use LabVIEW features in a TestStand system.


See Also

LabVIEW VI Options Dialog Box

Shortcuts Dialog Box


 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit