A while ago I blogged about Domain-Driven Design and how I like it so much. I mentioned that Tim McCarthy is writing a book that I'm pretty much looking forward to. Today he announced a new project on CodePlex for the source code of his upcoming book called .NET Domain-Driven Design with C#: Problem-Design-Solution. In order to wet your appetite, you can check out the slides and code of his talk about Domain-Driven Design using the ADO.NET Entity Framework. I recommend that you have a look.
The presentation starts out touching some of the key concepts and patterns of DDD. The second half explains what the ADO.NET Entity Framework means to DDD. In my humble opinion, the ADO.NET Entity Framework, in its current state, cannot be used in DDD scenarios. His impressions are indeed the same as mine:
Great Hope for the future, but Pain for the present
Indeed, my favorite O/R-mapper today is still NHibernate, although I'm still digesting its large and massive amount of features. Actually, I'm done with low level ADO.NET altogether. If you're not yet convinced that the ADO.NET Entity Framework in its current form is a bad idea, then give this a read. I'm still hoping for the best though, hopefully in a not too distant future.
