Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: .NET Domain-Driven Design with C#: Problem - Design - Solution ISBN: 978-0-470-14756-6
This is the forum to discuss the Wrox book .NET Domain-Driven Design with C#: Problem - Design - Solution by Tim McCarthy; ISBN: 9780470147566
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: .NET Domain-Driven Design with C#: Problem - Design - Solution ISBN: 978-0-470-14756-6 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Display Modes
  #1 (permalink)  
Old May 4th, 2009, 07:29 AM
Registered User
Join Date: May 2009
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Entity Framework

Hi Tim,

I just purchased your book on Domain Driven Design with C# and I am really enjoying it. Please forgive me if my question is similar to the one in the Persistence thread. On page 41, you mention that you originally intended to use the ADO.NET Entity Framework as your ORM solution. Since it was included in .NET 3.5 SP1, have you had a chance or desire to go back to your code for the book and re-implement that part using the Entity Framework? If so, where can I download or see the code? How would you have incorporated it into your code? Would the entity classes still be true POCO classes? Has anybody else incorporated the Entity Framework into the code from the book?

That was the biggest complaint of mine with the Entity Framework, that it was difficult to use true POCO, since it required the entity classes to derive from Entity Framework-specific classes, defeating the requirement to have the Domain Model independent of any persistence strategy. Microsoft has stated that this shortcoming will be addressed in the next version of the Entity Framework coming out with .NET 4.0.

Ron Kanagy
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Linq to SQL and the Entity Framework marko_ln BOOK: ASP.NET 3.5 Enterprise Application Development with Visual Studio 2008: Problem Design Solutio 4 February 25th, 2010 10:20 AM
The BeerHouse and Entity Framework docluv BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0 0 October 3rd, 2008 01:32 PM
changing host server framework 2.0 from framework jay_vijesh ASP.NET 1.x and 2.0 Application Design 1 September 11th, 2006 02:18 PM
Difference between Entity and Entity type arshad mahmood C++ Programming 0 May 8th, 2004 12:34 AM

All times are GMT -4. The time now is 04:49 PM.

Powered by vBulletin®
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.