title: Domain Driven Design and Entity Framework 4.1 (code-first)
body: <p>I am currently learning the domain driven design approach to development and using the .NET Domain Driven Design with C# book by Tim McCarthy as a guide.</p>
  
  <p>The book is really helpful but I'm becoming a bit unstuck when it comes to using the entity framework, in particular the code-first approach available in 4.1.</p>
  
  <p>Based on the example in the book, the layered architecture approach should mean the infrastructure layer can't see the model/domain one.</p>
  
  <p>So what's the best approach to mapping my domain poco's in the db context classes which (I assume) should sit in the infrastructure layer, without contravening the layered approach?</p>
  
  <p>There's a good chance I'm completely wrong with my thinking so please let me know as I'm still learning!</p>
  
  <p>Many thanks :)</p>
  
  <p>Adam</p>