title: Production Website Error After Model Change - The model backing the '-Context' context has changed since the database was created
body: <p>I have this project in Visual Studio that I recently published and hosted on IIS on a different machine. Initially I just backed up the localdb on my dev machine and restored it to the SQL Server on the production machine. Now I made an update to the website which required adding another property to the model. I updated the localdb by running add-migration. Everything is working fine on my dev machine.</p>
  <p>The database on the production server now has a lot of entries and I cannot lose the data. So I manually added a column via <code>ALTER TABLE dbo.Notes ADD ReadStatus nvarchar(MAX);</code>. But now the website throws this error. I tried adding the newly created __MigrationHistory entry from the dev machine to the __MigrationHistory table on the production machine, without fixing anything. I have read that dropping migrationhistory table may fix the problem but will result in data loss which will not work for me. Also tried adding <code>Database.SetInitializer&lt;YourDbContext&gt;(null);</code> as per <a href="https://stackoverflow.com/a/6214040/14199515">this S/O answer</a>.</p>
  <p>Question 1: How am I supposed to handle model changes to an MVC website after it is deployed? (e.g. there is no package manager console in IIS)</p>
  <p>Question 2: How does the website detect that there were model changes since the database was created? (it throws error even after I added the column to the database)</p>
  <p>This seems like such a simple problem, but I have been banging my head against a wall for hours now with no results. Any help would be awesome!</p>