title: How do architect an ASP.Net MVC app with EF?
body: <p>I'm having a little bit of trouble conceptualizing how to architect an MVC App with Entity Framework into a n-tiered app.</p>
  
  <p>The normal, textbook 3-tiered app should look something like </p>
  
  <p>Data Access->Business Logic->Presentation  </p>
  
  <p>The presentation shouldn't know anything about the data access.  With EF, ALL layers need to know about the model.  So my architecture now looks more like</p>
  
  <pre><code>Data Access-&gt;Business Logic
       |               |
        ---------------
               |
              MVC
  </code></pre>
  
  <p>Am I missing something here or am I thinking about this in the wrong way?  </p>
  
  <p>Should I be thinking of EF itself as the data access layer and put the entities in the business logic?</p>