title: EF 4.1 DbContext Generattor - Put Entities in different project?
body: <p>As a part of our application architecture, we like to define clear lines between our functional layers.  A typical application solution, therefore, will contain:</p>
  
  <ul>
  <li>Entity</li>
  <li>Model</li>
  <li>Task</li>
  <li>Presenter</li>
  <li>FrontEnd</li>
  </ul>
  
  <p>These end up being completely distinct assemblies.</p>
  
  <p>The Entity/Model delineation is done to keep database access functionality in a separate layer from our POCOs, so that only Task ever need know about Model, while everyone up to Presenter knows about Entity</p>
  
  <p>This works well when using Code-First or Fluent-API - but due to the lack of support for SPROCs in those paradigms, it turns out that under EF 4.1 I <em>must</em> use EDMX models. </p>
  
  <p>So - I'm generating POCOs using a DbContext Generator, but the resulting classes end up under .Model, and while I can force their namespace into .Entity instead, they still live in the .Model assembly, which means now .Presenter must reference .Model to get to classes that should be in .Entity.</p>
  
  <p>Is there a way to force or trick EF to dump its generated output into a different Project?</p>