title: How to Manage EF Migrations Between Development and Production Databases?
body: <p>Before anyone marks this as a duplicate, none of the questions similar to this addressed any of my concerns or answered any of my questions.</p>
  
  <p>I am currently developing all the POCOs and data contexts in a library project, and running migrations from within this project. The database I'm updating is the development database.</p>
  
  <p>What do I do if I want to create the current schema to a fresh, new database? I figure that all I have to do is to change the connection string in web.config and run Update-Database, correct? </p>
  
  <p>While the live/production database is up and running, I want to add new columns and new tables to the schema, and test it out in development. So I switch back the connection string to the development database's connection string, and run Update-Database.</p>
  
  <p>Going back and forth between two databases seems like I'll get conflicts between _MigrationHistory tables and the auto-generated migration scripts.</p>
  
  <p>Is it safe to manually delete the _MigrationHistory tables in both databases, and/or delete the migration files in /Migrations (so I'll run Add-Migration again)? How do we manage this?</p>