title: Difference between DB first and code first approach in EF?
body: <p>I'm a newbie at this and haven't quite got the grasp of DB first/Code first/POCO in EF. This is what I understand. Please let me know if this is accurate:</p>
  
  <ol>
  <li><p>In the DB first approach, the code is generated based upon an existing database. We can then choose to include tables/views/stored procedures. Tangentially, I see a lot of DB first approached where the database already has all the sprocs and the db. context only contains sprocs (function imports) but does not contain any table (db. set ) objects. In this case, why would you want to use EF? Why not just use ADO.Net with SQL Command?</p></li>
  <li><p>In the code first approach, the db. doesn't exist in the backend. the db. is generated using the POCO objects.</p></li>
  <li><p>POCO : Is this only used in code first? </p></li>
  </ol>