Skip to content

Update recommendation for separate migrations projects #5284

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AndriySvyryd merged 4 commits into from
Mar 25, 2026
+4 −1
Merged

Update recommendation for separate migrations projects #5284

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6c682f7
Update recommendation for separate migrations projects
AndriySvyryd Mar 6, 2026
fd81594
Apply suggestion from @Copilot
AndriySvyryd Mar 6, 2026
54c23eb
Clarify platform-specific project types and add IDesignTimeDbContextF…
Copilot Mar 25, 2026
a0e408b
Apply wording suggestion for platform-specific project types sentence
Copilot Mar 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion entity-framework/core/managing-schemas/migrations/projects.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ uid: core/managing-schemas/migrations/projects

# Using a Separate Migrations Project

You may want to store your migrations in a different project than the one containing your `DbContext`. You can also use this strategy to maintain multiple sets of migrations, for example, one for development and another for release-to-release upgrades.
You may want to store your migrations in a different project than the one containing your `DbContext`. This is recommended if your project uses a platform-specific project type, such as WinUI, Xamarin, MAUI, Blazor, or Azure Functions, or if it targets a specific runtime identifier (RID). You can also use this strategy to maintain multiple sets of migrations, for example, one for development and another for release-to-release upgrades.

> [!TIP]
> You can view this article's [sample on GitHub](https://github.com/dotnet/EntityFramework.Docs/tree/main/samples/core/Schemas/ThreeProjectMigrations).
Expand Down Expand Up @@ -59,3 +59,6 @@ Add-Migration NewMigration -Project WebApplication1.Migrations
```

***

> [!TIP]
> If your application uses dependency injection, consider implementing <xref:Microsoft.EntityFrameworkCore.Design.IDesignTimeDbContextFactory`1> in your migrations project. This allows the EF tools to create your `DbContext` without needing to run the startup project. For more information, see [From a design-time factory](xref:core/cli/dbcontext-creation#from-a-design-time-factory).
Loading