I just got on board with EF 5 and am using their code-first migrations tool but I seem to get an error when I try to enable migrations.
I type Enable-Migrations
into the package manager console and then it says
No classes deriving from DbContext found in the current project.
Edit the generated Configuration class to specify the context to enable migrations for.
Code First Migrations enabled for project MyApp.MvcUI.
It then creates a Migrations folder and a Configuration class in my MvcUI project. Thing is, my DbContext lives in a class library project called MyApp.Domain. It should be doing all that in that project and should have no problem finding my DbContext.
Oh wow, nevermind. I'm dumb.
In the Nuget package manager console there is a dropdown menu at the top labeled "Default Project:". Make sure you set that to the project you want to run the command against.
Hopefully this helps someone else avoid my embarrassing mistake.
There are actually 3 ways to make Nuget commands run in a specific project:
- [Package Manager Console] Set the active project in the dropdown at the top of the console toolwindow
- [Package Manager Console] Look for a parameter to specify the project. For some cmdlets I've seen -ProjectName and some use -Project
- [Solution Explorer] Right-click the project you want, and use the graphical package manager window (Manage NuGet Packages...).