title: Entity Framework Code First with DbUp
body: <p>I am thinking of using <code>Entity Framework 6</code> <code>Code First</code> for database interaction alongside <code>DbUp</code> for database schema update. The thing is I don't want to use <code>EF</code> migration for reasons. So, the workflow that I've reached to is:</p>
  
  <ol>
  <li>Change model (add <code>POCO</code>s, alter properties, etc)</li>
  <li>Run <code>Add-Migration temp_file</code> in <code>Visual Studio Package Manager Console</code></li>
  <li>Run <code>Update-Database -Script</code> in <code>Visual Studio Package Manager Console</code></li>
  <li>Grab the generated <code>sql</code> scripts including insertion of new row in table <code>__MigrationHistory</code></li>
  <li>Create a new <code>.sql</code> file and past the generated scripts</li>
  <li>Delete <code>temp_file</code>  </li>
  <li>Run DbUp</li>
  </ol>
  
  <p>It works perfectly locally and on production server, however I don't feel comfortable with adding and then deleting <code>temp_file</code> every time a new migration is generated (I wish there were a way to permanently stop <code>temp_file</code> being added to the solution.).</p>
  
  <p><strong>So question:</strong>
  Is there a better way to do database migration with <code>DbUp</code> using <code>Entity Framework</code>?</p>