Enterprise Library 3.0 Overview

Enterprise Library 3.0; as you have probably guessed, it is intended to take advantage of the new .NET Framework 3.0 features, but may be used with the .NET Framework 2.0 as well. This new version of the .NET Framework is not a major overhaul like from version 1.1 to 2.0. Instead, this version adds a lot of new features without changing much of the existing components of the .NET Framework 2.0. Some of these new features include the following:

• Windows Presentation Framework
• Windows Communication Framework
• Windows Workflow Foundation
• Windows CardSpace

Enterprise Library 3.0 adds new functionality and integration to go with these new features of the .NET Framework 3.0. It also does not introduce any breaking changes from Enterprise Library for .NET Framework 2.0. Currently there are two versions of Enterprise Library 3.0. Enterprise Library 3.0 - April 2007 release and Enterprise Library 3.1 - May 2007 release. The 3.1 version includes some fixes to the original 3.0 and an enhancement to the Policy Injection Application Block. For simplicity sake all versions of Enterprise Library 3.x will be referred to as simply Enterprise Library 3.0 in this book.

Validation Application Block
The Validation Application Block will allow developers to create validation rules that can be applied in the code to implicitly or explicitly validate properties and parameters. It will even support named validation, which allows a validation rule to be defined in the application configuration file and allows it to be applied to wherever the named validation rule is enforced within an application. This can give the application the flexibility to change rules applied to many fields in one central location without having to rebuild the application.

Policy Injection Application Block
The Policy Injection Application Block enables the policy-driven externalization of functionality and behaviors. You can specify policies (through configuration) that invoke functionality such as validation, exception handling, or logging, and you can attach these policies to specific types and methods in your applications through predicates, such as “All classes in the My.Application namespace” or “All methods with MyClass objects as parameters.” This allows the developer to create an application and then define which tasks or polices will be applied to the code via configuration data. This can be useful for specifying specific types of policies for different stages of the application’s life cycle.

Source of Information : The Definitive Guide To The Microsoft Enterprise Library


Subscribe to Developer Techno ?
Enter your email address:

Delivered by FeedBurner