title: Can't sync Entity Framework model and database
body: <p>I am new to Entity Framework and I'm inheriting a project that uses it. Currently I'm in a situation where everything appears to be in sync, but EF insists that they aren't. In short,</p>
  
  <ul>
  <li>All of my migrations appear in <code>[__MigrationsHistory]</code>, so I would assume they are all applied.</li>
  <li>When I try to start the WPF app backed by my model, I get the exception <code>The model backing the &lt;Database&gt; context has changed since the database was created.</code></li>
  <li>Given this, I assume there are changes in the model that need to be migrated to the database, so I run <code>Add-Migration Test</code> to see what EF thinks needs to be added. Herein lies the problem—the migration that's added tries to add things that already exist in the database. E.g., a create table statement for a table that's already there.</li>
  <li>If I run <code>Update-Database</code> after adding the above migration I get the expected error, <code>There is already an object named 'Table' in the database.</code></li>
  </ul>
  
  <p>At this point I'm suck. I'm in a loop where everything seems to be fine, but EF thinks it isn't. How do I reconcile things?</p>