Code first Enable migration error in Entity framework 6 MVC 5

Question

I'm using entity framework 6 with MVC 5 and trying to enable migration in code first so that I can avoid data loss. But when type the command in package manager console, it throws following error:

PM> Enable-Migrations -ContextTypeName [ContextClassName] The term 'Enable-Migration' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At line:1 char:1 + Enable-Migrations -ContextTypeName [ContextClassName] + ~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Enable-Migration:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException

I checked all duplicates but none of them worked in my case.

Does update-database work?

Neil
– Neil

2017-07-10 13:46:41 +00:00
Commented Jul 10, 2017 at 13:46 — Neil
– Neil, Commented Jul 10, 2017 at 13:46
stackoverflow.com/a/23154834/4361743

karman
– karman

2017-07-10 13:46:54 +00:00
Commented Jul 10, 2017 at 13:46 — karman
– karman, Commented Jul 10, 2017 at 13:46

Chris Pratt · Accepted Answer · 2017-07-10 14:20:29Z

3

There are two possible scenarios here.

Entity Framework is not installed or is installed incorrectly. If you do in fact have a reference to it, then first do:
```
PM> Uninstall-Package EntityFramework -Force
```
Then,
```
PM> Install-Package EntityFramework
```
Make sure to restart Visual Studio afterwards
You're actually using Entity Framework Core or you've added Entity Framework to an ASP.NET Core project running on the full framework. In either of these cases, none of the Entity Framework package manager commands will be available. If you've installed EF Core by mistake, remove it and install EF6 instead. If you've got an ASP.NET Core project, you must add a console app or class library running on the full framework for the EF6 reference. You'll manage all your entities here, as well as run your package manager commands against this project. The reason for this is that the EF6 package manager commands are incompatible with ASP.NET Core, even if you're running on the full framework.

answered Jul 10, 2017 at 14:20

Chris Pratt

240k37 gold badges414 silver badges469 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

LogicalDesk Over a year ago

great !! it worked the same way you told. thanks Chris

Collectives™ on Stack Overflow

Code first Enable migration error in Entity framework 6 MVC 5

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related