Preventing applications from using a newer XMS version

By default, when a newer XMS version is installed, the applications using the previous version automatically switch to the newer version without having to recompile.However, we can prevent applications from using the newer version by setting an attribute in the application configuration file.

The multiple versions coexistence feature ensures that installation of a newer XMS version does not overwrite the previous XMS version. Instead, multiple instances of similar XMS .NET assemblies coexist in the Global Assembly Cache (GAC), but have different version numbers. Internally, the GAC uses a policy file to route the application calls to the latest version of XMS. Applications run without a need for recompilation and can use new features available in the newer XMS .NET version.

Procedure

If an application is required to use the older XMS .NET version, set the publisherpolicy attribute to no in the application configuration file. Note: An application configuration file is a file with a name that consists of the name of the executable program to which the file relates, with the suffix .config. For example, the application configuration file for text.exe would have the name text.exe.config.

At any time, however, all the applications of a system use the same version of XMS .NET.

Parent topic: Developing XMS .NET applications