title: EF Core Model Snapshot out of sync between add-migration and update
body: <p>I'm using EF Core and code migrations.  It's my understanding that the snapshot file is supposed to be the "target database" to build future migration files off of.  </p>
  
  <p><strong>Situation:</strong> </p>
  
  <p>1) I did an add-migration to create a migration after some changes.  This updated the modelsnapshot which I guess is the expected behavior.<br>
  2) I then realized I realized I mis-typed one of my fields.  Instead of a string it was supposed to be a byte[]
  3) I made the changes to the classes
  4) I did add-migration again.  </p>
  
  <p>Now the DataSnapshot seems to be out of sync because the new add-migration does not include this type file change. </p>
  
  <p>It doesn't seem like I can do a remove-migration because no migration was actually applied to any database.  </p>
  
  <p>I know in EF6, this was a fine way to do it because it always targeted an actual database for the changes and not this snapshot file.  So just deleting the change file and remaking the change file was good enough.  </p>
  
  <p>This is the second time I've had to make some change to a migration file after realizing there was an issue (without actually running the update against anything) and both times were just incredible pains to try to fix the issue without wiping out all my previous migrations and starting over.  </p>
  
  <p>My question is how do I handle this now?  Should I be deleting both the change file and the snapshot file every time I do backtrack on an add migration?  </p>
  
  <p>I'm really concerned that I'm missing something here because now I have to make sure that not only is the change file correct but also the current snapshot is correct as well and if that snapshot ever goes out of sync, then I have to go and manually update it to </p>