The model backing the '--Context' context has changed since the database was created - but db is new production database
Just ran into the same error in ASP.Net application. In my case I did not use Code First, but I used standard ASP.Net authentication provider which apparently uses Code First, and authentication was broken because of this issue.
Here is quick and dirty solution is you don't care much about existing user records:
For me the solution was to drop the dbo.__MigrationHistory
table, authentication started working fine after that. Be aware! This solution is not for everyone! This will fix the problem, but it is potentially risky.
If you cannot afford to lose data in AspNet* tables:
ASP.Net authentication provider automatically creates tables in your database:
- AspNetRoles
- AspNetUsers
- AspNetUserRoles
- AspNetUserClaims
- AspNetUserLogings
The tables are empty by default, if you haven't created any new logins for your web site, you can use "quick and dirty" solution above. If you do care about preserving user information or just curios how Code First migrations work, follow these steps:
- Open your Web.config file and check the name of the connection string you have for your database. It will be one of the records under
<connectionStrings>
element. Open Package Manager Console:
Tools –> Library Package Manager –> Package Manager Console
- In Package Manager Console window, use a drop-down to set Default Project. Make sure this is the project that contains ASP.Net authentication provider code.
- Execute command:
Update-Database -ConnectionStringName MyConnectionStringName
Replace the MyConnectionStringName with the actual name you looked up in web.config.
As a result of this command you will see a new folder "Migrations" with a bunch of code generated by the Update-Database
command. Re-build and re-deploy your app, your new migration code will be executed on startup and would bring the database schema in sync with an updated version of ASP.Net authentication provider code.
When using Code First with Migrations, your database creates a table called __MigrationHistory
to track the current schema. When you run your application your Entity Framework will check this table to make sure that the database schema matches your database entities. If they do not match, you will get this error.
To update your database follow these steps:
- Open the Package Manager Console (View -> Other Windows -> Package Manager Console) in Visual Studio
- In the Package Manager Console Window, there is a drop down with your projects in, make sure it is set to the project that contains your
DbContext
- Make sure that the project that contains your
App.Config
/Web.Config
file is "Set as Startup Project" (If you have multiple Configs, it must be the one with the Database Connection String defined. - Type
Update-Database -ConnectionStringName MyConnString
whereMyConnString
is the name (not the actual connection string) of your connection string in yourApp.Config
/Web.Config
If you get an error like this: "Unable to update database to match the current model because there are pending changes and automatic migration is disabled."
You should enable Automatic Migrations and try again.To enable Automatic Migrations
- In the
Migrations
folder (in the project with yourDbContext
), openConfiguration.cs
. - Make sure the Constructor contains:
AutomaticMigrationsEnabled = true;
To stop Entity Framework/DbContext from monitoring changes on your database you could simply delete the __MigrationHistory
table in your database. It is then up to you to make sure that the database remains updated manually.
The solution from this is to use the static method SetInitializer and bind to the context a Null value. If you are working on a Web solution, the best position to write the code is in the Application_Start of your Global.asax.cs file.
protected void Application_Start() { AreaRegistration.RegisterAllAreas(); RegisterRoutes(RouteTable.Routes); //... Database.SetInitializer<MyContext>(null);}