When you migrate Sequence Call Adapter steps from 32-bit TestStand to 64-bit TestStand, you typically do not have to provide separate sequence files for each architecture because you can create bitness-independent sequences. However, for sequence files that reside in non-shared search directories, you must move the sequence files to a shared location before migrating, or you must copy the sequence files to the equivalent 64-bit location. The Sequence Call Adapter supports the $(Platform) path macro, and you can use the Engine.Is64Bit property in preconditions to write bitness-conditional code. You can also use the Engine.Is64Bit property in an expression to specify the path to a sequence file.

Additionally, when you migrate from 32-bit TestStand to 64-bit TestStand, you must consider the behavior of the CPU affinity and the remote execution settings for Sequence Call steps.