Export (0) Print
Expand All

Updating the Caching Application Block

Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

The latest Enterprise Library information can be found at the Enterprise Library site.

If a Caching Application Block update becomes available, you can install the update and have all applications use the updated version. However, if the updated version introduces compatibility problems for particular applications, you can install the updated version in the global assembly cache and configure some applications to use the updated version, while others continue to use the earlier version.

Updating Private Assemblies

If the Caching Application Block assembly has been deployed as a private assembly, you can deploy the update by replacing the earlier version of the DLL with the updated one in the application folder hierarchy.

Ff649197.note(en-us,PandP.10).gifNote:
You should keep a copy of the earlier version so that if you experience any compatibility issues with the updated assembly, you can revert to the earlier version.

Updating Shared Assemblies

The easiest way to update the Caching Application Block assembly in a shared configuration is to install the updated DLL in the global assembly cache. By default, the common language runtime tries to load the assembly that has the latest build and revision numbers, but the same major and minor version numbers, that the assembly the application was built with. Therefore, if the major and minor version numbers have not changed, adding the later version to the global assembly cache is expected to automatically update all applications that refer to the Caching Application Block assembly.

If the major or minor version numbers have been incremented, or if the updated version causes compatibility problems with existing applications, you can override the default version policy. To specify that a particular version of an assembly is used, edit the <BindingPolicy> of an application's configuration file (for individual applications) or the machine policy file. Alternatively, you can distribute the updated version of the assembly with a publisher policy file to redirect assembly requests to the updated version.

Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

The latest Enterprise Library information can be found at the Enterprise Library site.
Show:
© 2014 Microsoft