Editing VIs in LabVIEW Projects
- Updated2025-07-23
- 1 minute(s) read
Consider the following recommendations and requirements for editing VIs when you decide whether to use LabVIEW projects in a TestStand system:
- TestStand supports VIs organized in folders, LabVIEW project libraries, LabVIEW libraries, or LabVIEW packed project libraries defined in the LabVIEW project under the My Computer target. LabVIEW creates an application instance for each target in a LabVIEW project, including My Computer.
- VIs you call from TestStand in the context of a LabVIEW project cannot use global variables to share data with VIs outside of that project because when you open a VI specified in a LabVIEW project, the VI opens in the application instance for the project. LabVIEW also creates a main application instance that contains open VIs not included in a project and VIs you did not open from a project. Additionally, LabVIEW loads shared libraries in a unique application instance, which prevents naming conflicts with the VIs in the shared library or with VIs outside of the shared library.
- NI recommends using shared variables to transfer data between VIs executing in more than one
project. Note TestStand supports automatically deploying and undeploying shared variables defined in LabVIEW projects.
Related Information
- Organizing Test Program Files with LabVIEW Projects
- Organizing Test Program Files with LabVIEW Project Libraries
- Organizing Test Program Files with LabVIEW Libraries
- Organizing Test Program Files with LabVIEW Packed Project Libraries
- Deploying Network-Published Shared Variables
- Deploying VIs in LabVIEW Projects
- Updating and Patching VIs in LabVIEW Projects