Update-database in migration attempt after the model backing the 'productcontext' context has changed since the database was created. Consider using code

Question

1.50/5 (2 votes)

See more:

The model backing the 'ProductContext' context has changed since the database was created. Consider using Code

error show why plz help me
i was deleted migration folder then
1.enable-migration
2.add-migration "xxx"
3.update-database -f
after all step again same error

The model backing the 'ProductContext' context has changed since the database was created. Consider using Code

What I have tried:

update-database in migration attempt after The model backing the 'ProductContext' context has changed since the database was created. Consider using Code

Posted 7-Jun-17 21:29pm

vermanishad

Add a Solution

Comments

John C Rayan 8-Jun-17 4:01am

You need your migration folder for migrations. Why did you remove the migration folder , any reason? Try to restore the migration folder and try again.

Afzaal Ahmad Zeeshan 8-Jun-17 5:16am

Now try to use a database-first approach to get your migrations back, then start using the code-first.

I don't understand why you deleted the generated code files. It's impossible to go back or get back the migrations that you need to apply. However, there is a workaround that you delete everything that was created by Entity Framework and restart the process.

vermanishad 12-Jun-17 2:34am

i just checking migration folder when i will deleted then wht problems i will face but now it resolved

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)