From a85931a3f5943485ffe61762be0ea9e93bd86cc0 Mon Sep 17 00:00:00 2001 From: Oskar Josefsson Date: Thu, 16 Apr 2020 10:46:20 +0200 Subject: [PATCH] Missing update-database There should be an update-database after applying a blank merge before "continue developing" --- entity-framework/ef6/modeling/code-first/migrations/teams.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/entity-framework/ef6/modeling/code-first/migrations/teams.md b/entity-framework/ef6/modeling/code-first/migrations/teams.md index fa458e5fd9..ee845a2ef7 100644 --- a/entity-framework/ef6/modeling/code-first/migrations/teams.md +++ b/entity-framework/ef6/modeling/code-first/migrations/teams.md @@ -136,7 +136,8 @@ The following process can be used for this approach, starting from the time you 3. Run **Update-Database** to apply any new migrations that other developers have checked in. **_Note:_** *if you don’t get any warnings from the Update-Database command then there were no new migrations from other developers and there is no need to perform any further merging.* 4. Run **Add-Migration <pick\_a\_name> –IgnoreChanges** (for example, **Add-Migration Merge –IgnoreChanges**). This generates a migration with all the metadata (including a snapshot of the current model) but will ignore any changes it detects when comparing the current model to the snapshot in the last migrations (meaning you get a blank **Up** and **Down** method). -5. Continue developing, or submit to source control (after running your unit tests of course). +5. Run **Update-Database** to re-apply the latest migration with the updated metadata. +6. Continue developing, or submit to source control (after running your unit tests of course). Here is the state of Developer \#2’s local code base after using this approach.