This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

Disabling Publisher Policy

Now, assume you (as a system administrator) have deployed a publisher policy assembly (and the

latest version of the related assembly) to the GAC of a client machine. As luck would have it, nine of

the ten affected applications rebind to version 2.0.0.0 without error. However, the remaining client

application (for whatever reason) blows up when accessing CarLibrary.dll 2.0.0.0 (as we all know,

it is next to impossible to build backward-compatible software that works 100 percent of the time).

In such a case, it is possible to build a configuration file for a specific troubled client that

instructs the CLR to 

ignore the presence of any publisher policy files installed in the GAC. The

remaining client applications that are happy to consume the newest .NET assembly will simply be

redirected via the installed publisher policy assembly. To disable publisher policy on a client-by-

client basis, author a (properly named) *.config file that makes use of the 

element and set the apply attribute to no. When you do so, the CLR will load the version of the

assembly originally listed in the client’s manifest.