Send feedback on this topic.
Teradata.Client.Provider
Publisher Policy Administration
.NET Data Provider for Teradata > Developer's Guide > Working with the Data Provider Features > Side-by-Side Execution Overview > Publisher Policy Administration

The Publisher Policy File can be bypassed by specifying settings in the Application Configuration file or the Machine Configuration file.

Bypassing Publisher Policy

In the event that new versions of assemblies break an application, the programmer can use the following setting in the Application Configuration file to make the runtime system bypass the publisher policy:

<publisher Policy apply="no">

Redirecting Assembly Versions at the Application Level

The programmer can specify that an application use the newer version of the assembly by putting assembly binding information in the application configuration file.

Redirecting Assembly Versions at the Machine Level

There may be cases when a machine administrator wants all applications on a machine to use a specific version of an assembly; for instance, when it is desirable that every application use a particular assembly version because it fixes a security hole. If an assembly is redirected in the machine's configuration file, all applications using the old version will use the new version. The machine configuration file overrides the application configuration file and the publisher policy file.

Specifying Assembly Binding in Configuration Files

The application configuration file, machine configuration file, and publisher policy file use the same XML schema to process assembly redirection.

See Also

Redirecting Assembly Versions