Using TestStand Search Directories to Locate the Correct Code Module in 32-bit TestStand and 64-bit TestStand

TestStand 2019 Help

Edition Date: May 2019

Part Number: 370052AA-01

»View Product Info
Download Help (Windows Only)

By default, 32-bit TestStand and 64-bit TestStand do not share search directories. You can associate bitness-specific versions of a code module with a sequence or step type by placing the code module in a non-shared TestStand search directory, such as the <TestStand Public> directory. The TestStand <TestStand Public> directories use a (32-bit) or (64-bit) suffix to indicate the bitness of TestStand to which they belong. Search directories located under the <TestStand> installation directory, such as the <TestStand>\Components directory, are naturally separate because Microsoft Windows uses separate Program Files directories for 32-bit applications and 64-bit applications on 64-bit Windows, typically C:\Program Files (x86) for 32-bit applications and C:\Program Files for 64-bit applications.

When you migrate code modules installed in a non-shared search directory, such as the <TestStand Public> directory, from 32-bit TestStand to 64-bit TestStand, complete the following steps.

  1. Create a 64-bit search directory structure that matches the existing 32-bit search directory structure.
  2. Install the 64-bit compatible versions of each code module in the 64-bit directory in locations that match the 32-bit versions of the code module.

The existing 32-bit code modules and directory structure do not require changes. 32-bit TestStand finds the existing 32-bit code modules in the original locations.

Additionally, 32-bit TestStand and 64-bit TestStand cannot share platform-independent code modules, such as AnyCPU .NET DLLs, you reference in a non-shared search directory. You need two copies of the code module in this case to simultaneously support 32-bit TestStand and 64-bit TestStand. If you need to simultaneously support 32-bit TestStand and 64-bit TestStand, National Instruments recommends moving platform-independent code modules to a location 32-bit TestStand and 64-bit TestStand share so you can maintain a single copy of the code module.

If a Microsoft Visual Studio, LabWindows/CVI, or other development environment project resides in a search directory for which you enabled the Search Subdirectories option in the Edit Search Directories dialog box, ensure that the project does not create intermediate or output files from a 64-bit build in the 32-bit search directory or vice versa. When searching subdirectories, 32-bit TestStand might find the 64-bit version of the DLL code module first. When this happens, the 64-bit version of the DLL hides the 32-bit version of the DLL from 32-bit TestStand, causing steps that use the code module to fail because 32-bit TestStand cannot load the 64-bit DLL. Similarly, when searching subdirectories, 64-bit TestStand might find the 32-bit version of the DLL code module first. When this happens, the 32-bit version of the DLL hides the 64-bit version of the DLL from 64-bit TestStand, causing steps that use the code module to fail because 64-bit TestStand cannot load the 32-bit DLL.

WAS THIS ARTICLE HELPFUL?

Not Helpful