|Download Help (Windows Only)|
Complete the following steps to migrate platform-specific .NET assemblies, such as C++/CLI assemblies that contain unmanaged code, when you no longer intend to support the 32-bit architecture.
If the 64-bit version of the interface remains unchanged, TestStand sequences that depend on the code modules execute in 64-bit TestStand but no longer execute in 32-bit TestStand.
If you need to simultaneously support both architectures with a .NET code module but cannot use an AnyCPU assembly, create a 32-bit version of the assembly and a 64-bit version of the assembly and use one of the following techniques to associate the assembly with the adapter:
As an alternative to providing versions of a platform-specific .NET assembly for both platforms, you can call a non-matching bitness of a platform-specific assembly out-of-process using .NET remoting. Visit ni.com/info and enter the Info Code ex4g4q to access the National Instruments support article 5TUCSLXU, Can TestStand Call 64-Bit Code Modules?, for more information about this technique.