Deploying the Policy Injection Application Block as Shared Assemblies

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.

The Policy Injection Application Block assemblies are signed with a strong name. This is a recommended practice for security reasons. Both Visual Studio .NET and the .NET Framework SDK include tools to assign strong names. Strongly named assemblies can be deployed in a shared location for use by multiple applications. You can deploy the assembly in any file system location and add a <codeBase> element that specifies the location of the assemblies in the application configuration file of each application that uses the Policy Injection Application Block. For an explanation strong naming for the Enterprise Library assemblies, see Strong Naming Enterprise Library Assemblies.

A more likely scenario is that you deploy shared assemblies in the global assembly cache, which allows all applications on the computer to use the same assemblies. You can use one of the following tools to install an assembly in the global assembly cache, or you can drag and drop the assembly into the assembly folder:

  • An installer program, such as the Microsoft Windows Installer, version 2.0
  • The Global Assembly Cache tool command line utility (Gacutil.exe)
  • The .NET Framework Configuration Tool (Mscorcfg.msc)

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: