title: Code first approach versus database first approach
body: <p>I am working on an asp.net MVC 3 web application and I am using database first, but after I have mapped the DB tables into entity classes using entity framework, I am interacting with these tables as I will be interacting on the code first approach by dealing with Database tables as classes an objects. </p>
  
  <p>So after mapping the tables into entity classes I find that the code first approach and DB first are very similar but except of start writing the entities classes from scratch (as in code first) I have created the entity classes from existing database tables - which is easier and more convenient in my case.</p>
  
  <p><strong>So are there specific cases on which i will not be able to do some functionalities unless i am using one approach over the other which till now i cannot find any?</strong></p>