title: Best practice for using entity framework for post deployment database changes
body: <p>I am working on a ASP.NET Web Forms project which is expected to experience lots of database changes even after deployment.</p>
  
  <p>Our preference was to use Entity Framework 5, and the Database First design paradigm. However, since we have to make lots of changes to the database even after deployment, if I use database first approach, then every time I update my database, I will have to delete my entire model and regenerate it. Is there any best practices to make this process less painful?</p>