Microsoft   |   patterns & practices   |   Developer Network   |   Enterprise Library   |   Acceptance Testing Guide   |   Personal Site

Enterprise Library 6: Developer’s Guide Released - Grigori Melnik: Thoughts on Agile Software Engineering and Beyond - Site Home - MSDN Blogs

Enterprise Library 6: Developer’s Guide Released

Enterprise Library 6: Developer’s Guide Released

  • Comments 5

EntLib Dev Guide 2e coverJust in time for the MVP Global Summit, I’m excited to announce the second edition of our guide-primer on the latest Microsoft Enterprise Library. The guide explains the concepts that drove development of the blocks, the kinds of tasks they can accomplish, and how they help you implement many well-known design patterns. And, of course, it explains — by way of code extracts and sample programs — how you can actually use the blocks in your applications.

Keep in mind, the guide focuses on the following application blocks:

Data Access Application Block
Exception Handling Application Block
Transient Fault Handling Application Block
Logging Application Block
Semantic Logging Application Block
Policy Injection Application Block
Validation Application Block.

Unity Application Block and Unity Interception are covered in a separate sister guide on Dependency Injection with Unity which we released in August.

Both guides illustrate the usage of the application blocks in the context of individual code snippets and the larger reference implementation.

In the words of S. Somasegar, Corporate Vice-President, Microsoft Developer Division, who has written the foreword:

This guide is an absolute must read for anybody looking to put Enterprise Library into practice. Its clear and pragmatic advice is invaluable.

Here’s how to get it:

PDF (free download)

EPUB (free download)

Paperback via Amazon

Kindle edition via Amazon

Comments
  • BTW, if you are at the MVP Summit, attend our session on Semantic Logging on Thu, Nov 21, at 10:30 (B33 (Conference Center)/Rainier).

  • A worthy document for any developer/solution architect, but in the Data Access block I'm scratching my head as to why the Entity Framework (or ORM in general) isn't integrated.

  • @Attie

    Thanks for the feedback. The Data Access Application Block has a fundamentally different goal from an ORM. For DAAB it was to encapsulate the ADO.NET logic and relieve developers of the need to write duplicated code for common data access tasks (especially, when dealing with storprocs). If you are using EF, what would you need DAAB for?

  • Great I was looking for this kind of guide..   Thanks everyone who contribute for this

  • Thanks everyone very much ..

Page 1 of 1 (5 items)
Leave a Comment
  • Please add 6 and 8 and type the answer here:
  • Post