Beta for Enterprise Library Released by patterns & practices

pnp_logo BETA1 releases of Microsoft Enterprise Library 5.0 and Microsoft Unity 2.0 have been released by the patterns and practices team.

You’ll find improvements made to the overall Enterprise Library architecture and configuration experience in both of Enterprise Library and Unity. Enterprise Library is also easier to extend. Our Enterprise Library Contrib community has been active releasing additional providers and new blocks.

The new version runs side-by-side with earlier versions.

A new Developer Guide is being readied too.

For more information about the release, see Enterprise Library 5.0 Beta1 and Unity 2.0 Beta1 are released.

For more information, see patterns & practices.

About Enterprise Library

The Microsoft Enterprise Library is a collection of reusable software components (application blocks) designed to assist software developers with common enterprise development cross-cutting concerns (such as logging, validation, data access, exception handling, and many others). Application blocks are a type of guidance; they are provided as source code, test cases, and documentation that can be used "as is," extended, or modified by developers to use on complex, enterprise-level line-of-business development projects.

The design of application blocks encapsulates the Microsoft recommended and proven practices for .NET application development. These good practices are demonstrated in the overall design of the Enterprise Library, as well in the context-specific guidelines in the design of individual application blocks and QuickStarts. Software developers can add application blocks to .NET applications quickly and easily.

For more information, see Microsoft Enterprise Library.

About Microsoft Unity

The Unity Application Block (Unity) is a lightweight, extensible dependency injection container. It facilitates building loosely coupled applications and provides developers with the following advantages:

  • Simplified object creation, especially for hierarchical object structures and dependencies
  • Abstraction of requirements; this allows developers to specify dependencies at run time or in configuration and simplify management of crosscutting concerns
  • Increased flexibility by deferring component configuration to the container
  • Service location capability; this allows clients to store or cache the container
  • Instance and type interception

For more information, see Unity Application Block.

Bruce D. Kyle
ISV Architect Evangelist | Microsoft Corporation

cid:image010.png@01C9DEED.1FDB2200 cid:image011.png@01C9DEED.1FDB2200 cid:image012.gif@01C9DEED.1FDB2200 channel9

Add to Technorati Favorites

Bookmark and Share

Comments (0)

Skip to main content