Welcome to the new DAAB project site!

Nov 21, 2013 at 2:05 AM
The project is now open for community contributions!

We intend for this site to be the community hub and the primary channel for discussing everything related to DAAB. We want you to share your thoughts, criticisms, and suggestions. We’ll be doing planning and active development on this site.

To learn more about the official announcement to move to open development and what it means visit:

If you are interested in contributing code, please review our guidelines for all of the projects in the Enterprise Library family:

We look forward to engaging with you and making DAAB better.

patterns & practices team
Dec 3, 2013 at 1:52 PM
I've used LINQ to SQL classes and NHibernate for years. Now Entity Framework. All of these work by using mappings and creating objects from your data. With the ease of use of EF and LINQ to SQL classes, how does DAAB help us as .NET developers? Are there advantages here that I'm not aware of? Creating an object from my data seems more intuitive than using a dataset. Any thoughts on this are appreciated! Thanks.
Jan 14, 2014 at 5:23 AM
@dbrott, The Data Access Application Block is a wrapper around ADO.NET. It does provide accessors to provide one way object mapping so you don't have to use a Dataset if you don't want to. However, it's not an ORM and, from all accounts, will never be an ORM. So, if you have to (or want to) add some abstraction over ADO.NET the DAAB could help you but if you wish to use the features of an ORM then EF, NHIbernate, or perhaps some other micro-ORM would be a better choice.

Randy Levy
Enterprise Library support engineer
Support How-to