title: Domain Driven Design, .NET and the Entity Framework
body: <p>I'm new to domain driven design but want to learn it and use it for a new application.
  I will be using Entity Framework for data access.</p>
  
  <p>The basic layout so far is:</p>
  
  <blockquote>
    <p>ASP.NET MVC and other clients (mobile
    devices etc.)<br/>
    |<br/>
    Webservices<br/>
    |<br/>
    Domain Model (Services, Repositories, Aggregates, Entities and Value Objects)<br/>
    |<br/>
    Data Access Layer (Entity Framework)<br/>
    |<br/> Data Storage (SQL Server)<br/></p>
  </blockquote>
  
  <p>What is the best way to transfer data between the data access layer and the domain model?
  I'm thinking that the entities in the domain model are POCO objects and that they should be mapped to/from the Entity Framework objects. Is this a good solution?</p>
  
  <p>If so:<br/>
  How and where should such a mapping occur? (Domain Model Layer or Data Access Layer)<br/>
  Where and how should I query Entity Framework (ie. return a list based on a search)?</p>