Using Side-by-Side Versions of the LabWindows/CVI Run-Time Engine with TestStand
- Updated2025-03-28
- 1 minute(s) read
Using Side-by-Side Versions of the LabWindows/CVI Run-Time Engine with TestStand
Typically, the default LabWindows/CVI Run-Time Engine (RTE) is appropriate for most DLLs and applications you build in LabWindows/CVI to use with TestStand. However, on occasion, you might want to isolate a test system from upgrades or downgrades to the LabWindows/CVI RTE. With LabWindows/CVI 2012 or later you can isolate LabWindows/CVI applications and DLLs from upgrades or downgrades to the LabWindows/CVI RTE by binding an executable or DLL to a specific, side-by-side version of the LabWindows/CVI RTE. Refer to the Binding Executables and DLLs to Side-by-Side Run-Time Engines topic in the LabWindows/CVI Help for more information about binding executables and DLLs to a side-by-side version of the LabWindows/CVI RTE.
Calling DLLs that Use a Side-by-Side Version of the LabWindows/CVI RTE in TestStand
You can use the LabWindows/CVI Adapter and the C/C++ DLL Adapter in TestStand to load and call DLL code modules that use a side-by-side LabWindows/CVI RTE or the default LabWindows/CVI RTE within the same sequence file. However, TestStand does not support calling DLLs you create with tools other than LabWindows/CVI, such as Microsoft Visual Studio, to use a side-by-side LabWindows/CVI RTE.
Related Information
- Programming with the TestStand API in LabWindows/CVI
- Organizing Test Program Files with LabVIEW-Built Shared Libraries
- Binding a TestStand Custom User Interface to a Side-by-Side Version of the LabWindows/CVI RTE
- Choosing Between the Shared or Side-by-Side Version of the LabWindows/CVI Run-Time Engine
- Identifying Components to Deploy