Enterprise Library 5.0 Release

Microsoft Enterprise Library is a popular collection of reusable software components (called application blocks) designed to address common cross-cutting concerns of enterprise application developers (such as logging, validation, data access, exception handling, and more). Entlib is provided as source code, test cases, and documentation that can be used “as is” or extended, and encapsulates the Microsoft recommended and proven practices for .NET application development.Well,just heard about Microsoft has released its Enterprise Library 5.0 (April 2010).Was eager to look in the new blocks shiped with it and want to share the same with you.
I was just going through the older versions of releases and found:
There have been several versions of the Microsoft Enterprise Library:
• Enterprise Library 5.0 (April 2010) – Current
• Enterprise Library 4.1 (October 2008) – Active
• Enterprise Library 4.0 (May 2008) – Active
• Enterprise Library 3.1 (May 2007) – Active
• Enterprise Library 3.0 (April 2007) – Deprecated
• Enterprise Library 2.0 (January 2006) – Active/Retired
• Enterprise Library 1.1 (June 2005) – Deprecated
• Enterprise Library 1.0 (January 2005) – Deprecated
What’s new in v 5.0?
Version 5.0 does not add any new Application Blocks, but instead concentrates on improving what was there in v 4.1. The available application blocks are:
• Caching Application Block
• Cryptography Application Block
• Data Access Application Block
• Exception Handling Application Block
• Logging Application Block
• Policy Injection Application Block
• Security Application Block
• Unity Application Block
• Validation Application Block
Microsoft has released Enterprise Library 5.0 and it’s available for download now.
Just to describe in little more words According to MSDN site
• Major architectural refactoring that provides improved testability and maintainability through full support of the dependency injection style of development
• Dependency injection container independence (Unity ships with Enterprise Library, but you can replace Unity with a container of your choice)
• Programmatic configuration support, including a fluent configuration interface and an XSD schema to enable IntelliSense
• Redesign of the configuration tool to provide:
– A more usable and intuitive look and feel
– Extensibility improvements through meta-data driven configuration visualizations that replace the requirement to write design time code
– A wizard framework that can help to simplify complex configuration tasks
• Data accessors for more intuitive processing of data query results
• Asynchronous data access support
• Honoring validation attributes between Validation Application Block attributes and DataAnnotations
• Integration with Windows Presentation Foundation (WPF) validation mechanisms
• Support for complex configuration scenarios, including additive merge from multiple configuration sources and hierarchical merge
• Optimized cache scavenging
• Better performance when logging
• Support for the .NET 4.0 Framework and integration with Microsoft Visual Studio 2010
• Improvements to Unity
• A reduction of the number of assemblies