Why is code first migrations EF asking to create new migration, when already exists?

Question

0.00/5 (No votes)

See more:

So i loaded up an old project to fix a bug.

The project tries to run the initialiser, but upon doing so complains that there are pending database changes, or the model is incorrect etc.

So my questions are:

1) Why is it requesting another migration to be addded to run succesffuly, when the site has gone live and already works fine?

2) Why is it scaffolding a migration that already exists?

What I have tried:

Add-Migration in the console, and it scaffolds the migration. However the newly scaffolded migration is exactly the same as the pre-existing "Intial_Create" migration (this is the 1 and only migration).

Posted 23-Nov-16 0:22am

Grant Weatherston

Updated 23-Nov-16 6:41am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mohtshm Zubair · Accepted Answer · 2016-11-23T06:09:00

Plz first take backup of your project. Then follow these steps.

Go to the project (if multiple projects) Which have EF context class. Delete the [Migration] folder.

Then go in Nuget Package Manager Console.

And in dropdown select the project (if multiple projects). And then run following commands to get things OK for EF.

Enable-Migrations

This will generate again the migration folder

Then again fire command in Nuget Con...

Add-Migration 'with any message'

This will push things if any pending changes there

then again fire last command

Update-Database

Now ur Ef is OK back again