Export (0) Print
Expand All

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

Applications that use the Logging 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 Logging Application Block as Private Assemblies

If the application does not have to use the services available from the global assembly cache, the Logging Application Block assemblies can be deployed in the application directory structure. This simplifies deployment because you can install the whole application, including the Logging Application Block assemblies, on the destination computer by using the xcopy command. If multiple applications on the same computer use the Logging Application Block, you can install a copy of the assemblies in each application folder hierarchy. This enables each application's copy of the assemblies to be independently updated. For information about adding strong names to an Enterprise Library assembly, see Strong Naming Enterprise Library Assemblies.

Deploying the Logging Application Block as Shared Assemblies

You can assign a strong name to the Logging Application Block assemblies. This is a recommended practice for security reasons. Both Visual Studio .NET and the .NET Framework SDK include tools to assign strong names. After assemblies are strong named, they can be deployed in a shared location and used by multiple applications. You can choose to 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 Logging Application Block.

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

  • Use an installer program, such as the Microsoft Windows Installer, version 2.0.
  • Use the Global Assembly Cache Tool command line utility (Gacutil.exe).
  • Use the .NET Admin MMC snap-in (Mscorcfg.msc).
  • Drag and drop the assembly into the assembly folder.

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