diff --git a/docs/en/release-info/migration-guides/abp-11-0.md b/docs/en/release-info/migration-guides/abp-11-0.md index e2b69a6471..fa9746e07a 100644 --- a/docs/en/release-info/migration-guides/abp-11-0.md +++ b/docs/en/release-info/migration-guides/abp-11-0.md @@ -136,6 +136,31 @@ ABP v11.0 uses EF Core 11. These database providers have no stable EF Core 11 re - Keep Oracle and Devart applications on ABP v10.x until the provider ships an EF Core 11 version. - Pomelo 9.0.0 targets EF Core 9, so it doesn't work on ABP v10.x either. +### EF Core Tools No Longer Reference EF Core Design + +**Who is affected** + +- Applications whose migration startup project references `Microsoft.EntityFrameworkCore.Tools` but not `Microsoft.EntityFrameworkCore.Design`. Older startup templates added only `Microsoft.EntityFrameworkCore.Tools`. + +**What changed** + +`Microsoft.EntityFrameworkCore.Tools` 11.0 no longer depends on `Microsoft.EntityFrameworkCore.Design`. Without it, `dotnet ef` commands fail: + +``` +Your startup project 'Acme.BookStore.EntityFrameworkCore' doesn't reference Microsoft.EntityFrameworkCore.Design. This package is required for the Entity Framework Core Tools to work. +``` + +**What to do** + +Add `Microsoft.EntityFrameworkCore.Design` to the migration startup project. If you pass `--startup-project`, add it to that project: + +```xml + + all + runtime; build; native; contentfiles; analyzers + +``` + ### Static Assets on .NET 11.0.1xx SDKs **Who is affected**