Here I will explain how to migrate when there are two separate db contexts in two separate projects in the same solution.
The format for migration commands are as follows:
enable-migrations -ContextTypeName <DbContext-Name-with-Namespaces> -MigrationsDirectory:<Migrations-Directory-Name>
DbContext-Name-with-Namespaces - This is the full path to the database context class (including namespace)
Add-Migration -configuration <DbContext-Migrations-Configuration-Class-with-Namespaces> <Migrations-Name>
DbContext-Migrations-Configuration-Class-with-Namespaces - This is the full path to the configuration class (including namespace), which was created in the previous step.
Update-Database -configuration <DbContext-Migrations-Configuration-Class-with-Namespaces> -Verbose
Example:
1) In the Nuget Package Manager Console, make sure to select the "Default Project". That is the project which the migrations is going to happen.
2) Also if the startup project contains a App.Config, you need to add the ConnectionString 's for the two context there as well.
3) Enable migrations
PM> Enable-migrations -ContextTypeName:My.Notification.ServicesMock.Data.MyMockContext -MigrationsDirectory:MyMigrations
Result:
Checking if the context targets an existing database...
Code First Migrations enabled for project My.Notification.ServicesMock.
Now you will see a migrations directory been created in your project as "MyMigrations", which contains the configuration class. Later on, the migrations will be added to that folder.
4) Add Migration
PM> Add-Migration -configuration My.Notification.ServicesMock.MyMigrations.Configuration "Initial"
Result:
Scaffolding migration 'Initial'.
The Designer Code for this migration file includes a snapshot of your current Code First model. This snapshot is used to calculate the changes to your model when you scaffold the next migration. If you make additional changes to your model that you want to include in this migration, then you can re-scaffold it by running 'Add-Migration Initial' again.
5) Update database
PM> Update-Database -configuration My.Notification.ServicesMock.MyMigrations.Configuration -verbose
Result:
Using StartUp project '...'.
Using NuGet project '...'.
Specify the '-Verbose' flag to view the SQL statements being applied to the target database.
Applying explicit migrations: [61401174_Initial].
Running Seed method.
Your migrations are complete now. Have a look in the Db.
The format for migration commands are as follows:
enable-migrations -ContextTypeName <DbContext-Name-with-Namespaces> -MigrationsDirectory:<Migrations-Directory-Name>
DbContext-Name-with-Namespaces - This is the full path to the database context class (including namespace)
Add-Migration -configuration <DbContext-Migrations-Configuration-Class-with-Namespaces> <Migrations-Name>
DbContext-Migrations-Configuration-Class-with-Namespaces - This is the full path to the configuration class (including namespace), which was created in the previous step.
Update-Database -configuration <DbContext-Migrations-Configuration-Class-with-Namespaces> -Verbose
Example:
1) In the Nuget Package Manager Console, make sure to select the "Default Project". That is the project which the migrations is going to happen.
2) Also if the startup project contains a App.Config, you need to add the ConnectionString 's for the two context there as well.
3) Enable migrations
PM> Enable-migrations -ContextTypeName:My.Notification.ServicesMock.Data.MyMockContext -MigrationsDirectory:MyMigrations
Result:
Checking if the context targets an existing database...
Code First Migrations enabled for project My.Notification.ServicesMock.
Now you will see a migrations directory been created in your project as "MyMigrations", which contains the configuration class. Later on, the migrations will be added to that folder.
4) Add Migration
PM> Add-Migration -configuration My.Notification.ServicesMock.MyMigrations.Configuration "Initial"
Result:
Scaffolding migration 'Initial'.
The Designer Code for this migration file includes a snapshot of your current Code First model. This snapshot is used to calculate the changes to your model when you scaffold the next migration. If you make additional changes to your model that you want to include in this migration, then you can re-scaffold it by running 'Add-Migration Initial' again.
5) Update database
PM> Update-Database -configuration My.Notification.ServicesMock.MyMigrations.Configuration -verbose
Result:
Using StartUp project '...'.
Using NuGet project '...'.
Specify the '-Verbose' flag to view the SQL statements being applied to the target database.
Applying explicit migrations: [61401174_Initial].
Running Seed method.
Your migrations are complete now. Have a look in the Db.