|Download Help (Windows Only)|
When a type conflict occurs, selecting to use the later version number of a type can propagate unwanted type versions to all instances of the type. For example, unwanted propagation might occur in the following situations:
Because you can save sequence files to previous versions of TestStand but some types might not run correctly on previous versions of TestStand, you can specify the earliest version of TestStand that can run a type. Enable the Set Earliest TestStand Version that can Use this Type option on the Version tab of the Step Type Properties dialog box or on the Version tab of the Type Properties dialog box and set the earliest version to the current version of TestStand to prevent the current version of a type from being used in or accidentally propagated to an earlier TestStand version.
You can also create different versions of the type to run in different versions of TestStand. When you save a sequence for a previous version of TestStand, TestStand searches a set of compatibility directories to find the type version that is compatible with the previous version for which you want to save the sequence file. TestStand saves the types from the type palette files in the <TestStand>\Components\Compatibility\<version number> and <TestStand Public>\Components\Compatibility\<version number> directories with the sequence file. You can place type palette files from earlier versions of TestStand in the <TestStand Public>\Components\Compatibility\<version number> directory to ensure that TestStand saves the correct version of the types with the sequence file.