title: EF Code First - Cached migration data?
body: <p>Does Entity Framework Code First Migrations store its migration data anywhere else other than the target database and the <code>Migrations</code> folder?</p>
  
  <p>I have an odd scenario where I've added a brand new .NET model class, and added it to my datacontext - but for some reason it's not being added to the generated DbMigration when I do an <code>Add-Migrations</code>. It's as if EF thinks it's already there. What confirms my suspicion that EF thinks it's already there is that if I comment out some of the properties in my new .NET class, the generated DbMigration then contains calls to <code>DropColumn</code> to remove those properties! I don't understand this though, as I've completely deleted the target database, and removed any migration files that have anything to do with that class. I don't understand how EF knows those properties were ever there.</p>
  
  <p>I've tried explicitly specifying the connection string when running <code>Update-Database</code> and <code>Add-Migration</code>, to make sure that it's not connecting to another copy of the database somewhere. This doesn't make a different though.</p>
  
  <p>Does EF cache the data somewhere? Is there some other place this information is stored?</p>