|Download Help (Windows Only)|
When you load a file that contains a type definition and another type definition with the same name already exists in memory, TestStand compares the two type definitions, including all the built-in and custom subproperties in the types.
If the types are identical, TestStand continues to use the type in memory. If the types are not identical, TestStand attempts to resolve the type conflict. TestStand automatically selects the type with the latest version number when all of the following conditions exist:
If TestStand cannot automatically resolve a type conflict, TestStand either launches the Type Conflict in File dialog box or, if TestStand is loading a file an execution calls, returns a run-time error.
|Note If an execution calls a file that has a later version of a type than the type version currently loaded in memory, TestStand does not automatically resolve the conflict and instead returns a run-time error. Replacing a type definition while an execution is running is unsafe because the execution might be using the type.|
The Type Conflict in File dialog box prompts you to resolve the conflict. You can select to use or rename the type currently loaded in memory or use or rename the type in the file you are attempting to load. When you select to use one of the two versions of the type, TestStand converts all instances of the type to match the type version you select. If you rename one of the two versions of the type, TestStand modifies the instances of the type in memory that refer to the version of the type you select to refer to the renamed version.
|Note Type instances not in memory refer to the original name for the type and might cause additional conflicts when you load them.|