Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 9
    All the philosophical theories fall right to the ground when you tell them "I don't want to duplicate all my entities into DTOs simply because I don't need it and it violates DRY, and I also don't want my client application to take a dependency on EntityFramework.dll". "Entities" in the Entity Framework jargon are not the same as "Entities" as in "Domain Model" Commented Oct 6, 2013 at 19:02
  • I'm ok with duplicating my domain entities into a DTO, using an automated tool like Automapper, if that's what it takes. I'm just not sure how that is supposed to look like at the end of the day. Commented Oct 6, 2013 at 23:05
  • 22
    I would recommend you to watch Jimmy Bogard's NDC 2012 session "Crafting Wicked Domain Models" on Vimeo. He explains what rich domain should be and how to implement them in real life by having behaviour in your entities. Examples are very practical and all in C#. Commented Oct 7, 2013 at 22:48
  • 1
    thanks so much for linking, and for others reading this even if you think you aren't interested in that specific topic, suggest to check out the other videos - NDC is very high quality vimeo.com/ndcoslo/videos Commented Oct 14, 2013 at 0:57
  • 3
    I demand love for Java too :/ Commented Feb 12, 2016 at 15:07