EF Migration object already exists error

asp.net-mvc c# ef-code-first entity-framework

Question

I am working on an ASP.NET MVC project with Entity Framework with code first from database. I get the models for each table in the database. I made some changes in the models, enabled migrations and when I initial the migration I get an error:

There is already an object named 'TableName' in the database."

I tried with update-database -force but didn't help. The initial migration creates the tables that already exist!

How to make the initial migration apply the changes on the models and not create the tables from beginning?

And what is the best practice to sync changes between database and models in this case?

1
15
6/30/2016 5:01:19 PM

Accepted Answer

try to Run the

Add-Migration InitialCreate –IgnoreChanges 

command in Package Manager Console. This creates an empty migration with the current model as a snapshot. and then Run the

Update-Database 

command in Package Manager Console. This will apply the InitialCreate migration to the database. Since the actual migration doesn’t contain any changes, it will simply add a row to the __MigrationsHistory table indicating that this migration has already been applied.

see this

then change your models and add migration.

another approach is to simply comment all the code on up and down methods

27
6/30/2016 4:50:07 PM

Popular Answer

Best and working For me idea is to comment all the code in UP and Down functions of Initial migration file and then fire dotnet ef database update this should work fine,make sure you update migration before commenting out initial migration



Related Questions





Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow