Deploying the Security 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.

The Security Application Block is comprised of multiple assemblies. Each assembly belonging to the Security Application Block has a file name that begins with Microsoft.Practices.EnterpriseLibrary.Security. Additionally, the application block depends on the Enterprise Library Core. Depending on the configuration of the application using the application block, it may also require the Data Access Application Block and Caching Application Block assemblies. Applications that use the Security Application Block can be deployed in one of two configurations:

  • They can be deployed as private assemblies in the application folder hierarchy.
  • They can be deployed as shared assemblies in any file system location or in the global assembly cache.

Deploying the Security Application Block as Private Assemblies

If the application does not have to use the services available from the global assembly cache, the Security Application Block can be deployed in the application folder structure. This simplifies deployment because you can install the whole application, including the Security Application Block assemblies, on the destination computer by using the xcopy command. If multiple applications on the same computer use the Security Application Block, you can install a copy of the assemblies in each application folder hierarchy. This allows each application's copy of the assemblies to be updated independently.

Deploying the Security Application Block as Shared Assemblies

You can assign a strong name to the Security Application Block assemblies. Both Visual Studio .NET and the .NET Framework SDK include tools to do this. After assemblies are strong named, they can be deployed in a shared location and used by multiple applications. You can choose to deploy the assemblies in any file system location and add a <codeBase> element specifying the location of the assemblies in the application configuration file of each application that uses the Security Application Block. For information on strong naming Enterprise Library assemblies, see Strong Naming Enterprise Library Assemblies.

A more likely scenario is that you deploy shared assemblies in the global assembly cache. In this scenario, all applications on the computer can use the assemblies without any additional configuration. You can use one of the following tools to install an assembly in the global assembly cache:

  • 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: