Reputation: 23749
Following this Microsoft Tutorial when I run the PM> Add-Migration MyFirstMigration
command in VS2015 project created from the same tutorial I get the following error that I can't resolve:
More than one DbContext was found. Specify which one to use.
Use the '-Context' parameter for PowerShell commands and the '--context' parameter for dotnet commands.
Point to note
Individual User Account
authentication instead of No Authentication
used in the tutorial.ASP.NeT Core 1.0 and VS2015-Update 3 on windows 8.1
Upvotes: 56
Views: 89125
Reputation: 205
[--context]
The DbContext class to use. Class name only or fully qualified with namespaces. If this option is omitted, EF Core will find the context class. If there are multiple context classes, this option is required.
Add-Migration MyMigration -context DataContextName
Upvotes: 1
Reputation: 21
Use below to commands:
PM> Add-Migration MyFirstMigration -Context YourDbContext
PM> update-database -Context YourDbContext
Upvotes: 1
Reputation: 23749
Running the following command (obtained from this article) and a response from @Maverik (from StackOverflow here) and a suggestion from @doctor above helped me resolved the issue. Thank you all for your help:
PM> Add-Migration MyFirstMigration -Context BloggingContext
Upvotes: 77
Reputation: 73
Add-Migration MyFirstMigration -Context DbContextName
It does work in my project.
Upvotes: 2
Reputation: 6007
If you need only update a identity schema existent, try it:
update-database -Context ApplicationDbContext
ApplicationDbContext = your identity context
Upvotes: 16
Reputation: 433
The error clearly explains to mention --context with db Context name if more than one DbContext. So try by mentioning your DbContext name.
dotnet ef migrations add Initial --context SampleDbContext
Hope this helps.
Upvotes: 19
Reputation: 114
that because you have two DbContext in your solution. First is default created when you creating project(ApplicationDbContext) and second your EF DbContext. Solution is described in error message just specify your EF DbContext
Upvotes: 4