You must explicitly add user interface files to the deployment. If you are using a TestStand workspace to create a deployment, create a new project for the user interface that includes all the required files and add the user interface project to the workspace. If you are using a directory to create a deployment, ensure that the directory you use includes a copy of all the required user interface files.

Enable the Include Without Processing Item or Dependencies option in the File Properties section on the Distributed Files tab of the TestStand Deployment Utility for the user interface files for the deployment utility to include the user interface without modifications and without detecting dependencies because user interfaces and dependent files are designed to work together without modification.

Modifying the Built-In LabVIEW Simple or Full-Featured User Interface Examples

When you run the TestExec.exe build specification to generate an executable, LabVIEW prefixes VIs listed under the Dependencies node in the LabVIEW project with Simple UI — or Full UI — for the simple and full-featured user interfaces, respectively, to avoid name collisions. If you load any VI from the user interface by name, you must update the code that loads the VI to include VI prefixes.

Complete one of the following options for all dynamic calls listed under the Dependencies node, including VIs that you call from top-level files but that you have not explicitly added to the My Computer target in the LabVIEW project, to resolve this issue:

  • Add the Simple UI — or Full UI — prefix to the path you pass to the Open VI Reference function when the caller VI runs in the LabVIEW RTE. You can use the Application:Kind property in LabVIEW to determine whether the VI is running in the development system or the LabVIEW RTE.
  • Add the VIs listed under the Dependencies node to the My Computer target to prevent the name change when you build the executable. LabVIEW prefixes only the files listed under the Dependencies node. NI recommends that you prefix these VIs manually to avoid potential name collisions that might prevent the user interface from running VIs that have conflicting names.