Share via

Design of Enterprise Library

  • Article
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.

Enterprise Library incorporates a set of best practices in its overall design. Among these are the following:

  • It uses common application block functionality (the Enterprise Library Core).
  • It uses uniform conventions for naming and versioning.
  • It incorporates instrumentation into all application blocks.
  • It uses unit tests written during the design phase.

The section describes the design of Enterprise Library and includes the following topics:

  • Design Patterns. This topic describes the use of design patterns within Enterprise Library.
  • The Enterprise Library Core. This topic describes the Enterprise Library Core, including the configuration system.
  • Providers. This topic describes the use of providers to implement extensibility.
  • Design-Time Configuration. This topic describes the design-time configuration features of Enterprise Library.
  • Instrumentation. This topic describes the implementation of instrumentation within Enterprise Library.
  • The Injection Model. This topic describes the Injection model, including the Unity Application Block (also known as Unity) and ObjectBuilder.
  • Group Policy and WMI Support. This topic describes Group Policy and Windows Management Instrumentation (WMI) support using the Manageable Configuration Source.
  • Unit Tests. This topic describes the use of unit tests within Enterprise Library.