title: Generate POCO classes from model using T4 templates vs. EF4.1 simplified API Model First approach
body: <p>I have model created with visual designer. Now I want to have POCO classes generated from it. In another question of mine, EF4.1 simplified API Model First approach was suggested to me. Before I was also thinking about T4 templates.</p>
  
  <p>What are the limitation of EF4.1 simplified API Model First comparing to using T4 templates to generate POCO classes ? What are advantages to of EF4.1 approach if any (besides it is supposed to be simpler to use)? My decision now will be very hard to undone as I will have quite huge persistence layer, so it might be hard to make changes to it in future.</p>
  
  <p>Particularly, I'm interested in this features:</p>
  
  <ul>
  <li>can I get either of those 2 options to generate database tables every time I change model (in visual designer) so I don't have to generate queries and run them ? That would speed up my development process a lot (for some reason I have to drop tables manually every time I change model so it takes a lot of time). I know this can be done with </li>
  <li>can I have POCO classes in another project ? I know this can be dome with T4 templates but is it also possible with simplified API?</li>
  <li>can properties in generated POCO classes be annotated without being overwritten every time they gets regenerated from model ? (this is indeed possible with code-first approach)</li>
  <li>is there any difference in efficiency? </li>
  </ul>
  
  <p>If it matters any technology chosen will be used in ASP.NET MVC application.</p>
  
  <hr>
  
  <p><strong>EDIT:</strong>
  Please answer any subquestion of my question if you know the answer. Maybe together with another partial answer it will give me the information I need. Thank you</p>