From 6cd90c4cd9a9019dc9b3d03e887635d79ddda054 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Wed, 26 Feb 2025 14:17:35 -0500 Subject: [PATCH 1/4] Update EF Core tooling breaking change --- .../tutorials/movie-database-app/part-2.md | 74 +++++++------------ 1 file changed, 26 insertions(+), 48 deletions(-) diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md index 3fc646444c21..149d478b8a2b 100644 --- a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md +++ b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md @@ -119,8 +119,6 @@ Paste all of the following commands at the prompt (`>`) of the **Terminal**. Whe When you paste multiple commands, all of the commands execute except the last one. The last command doesn't execute until you press Enter on the keyboard. -:::moniker range=">= aspnetcore-10.0" - ```dotnetcli dotnet tool install --global dotnet-aspnet-codegenerator dotnet tool install --global dotnet-ef @@ -136,56 +134,36 @@ dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore > [!IMPORTANT] > After the first eight commands execute, make sure that you press Enter on the keyboard to execute the last command. -:::moniker-end - :::moniker range=">= aspnetcore-9.0 < aspnetcore-10.0" -```dotnetcli -dotnet tool install --global dotnet-aspnet-codegenerator -dotnet tool install --global dotnet-ef -dotnet add package Microsoft.EntityFrameworkCore.SQLite -dotnet add package Microsoft.VisualStudio.Web.CodeGeneration.Design -dotnet add package Microsoft.EntityFrameworkCore.SqlServer -dotnet add package Microsoft.EntityFrameworkCore.Tools -dotnet add package Microsoft.AspNetCore.Components.QuickGrid -dotnet add package Microsoft.AspNetCore.Components.QuickGrid.EntityFrameworkAdapter -dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore -dotnet add package Microsoft.EntityFrameworkCore.Design -``` - -> [!IMPORTANT] -> After the first nine commands execute, make sure that you press Enter on the keyboard to execute the last command. - -Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: - -```diff - - runtime; build; native; contentfiles; analyzers; buildtransitive - all -+ true - -``` - -The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The change to the package reference can be reverted in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). - -:::moniker-end - -:::moniker range="< aspnetcore-9.0" - -```dotnetcli -dotnet tool install --global dotnet-aspnet-codegenerator -dotnet tool install --global dotnet-ef -dotnet add package Microsoft.EntityFrameworkCore.SQLite -dotnet add package Microsoft.VisualStudio.Web.CodeGeneration.Design -dotnet add package Microsoft.EntityFrameworkCore.SqlServer -dotnet add package Microsoft.EntityFrameworkCore.Tools -dotnet add package Microsoft.AspNetCore.Components.QuickGrid -dotnet add package Microsoft.AspNetCore.Components.QuickGrid.EntityFrameworkAdapter -dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore -``` + > [!IMPORTANT] -> After the first eight commands execute, make sure that you press Enter on the keyboard to execute the last command. +> If using the .NET 9 SDK, a breaking change in EF Core tooling prevents scaffolding from executing with the following exception: +> +> > :::no-loc text="Could not load file or assembly 'Microsoft.EntityFrameworkCore.Design, Version=9.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified."::: +> +> Adopt ***either*** of the following approaches: +> +> * Use a .NET SDK for .NET 10 or later. .NET 10 is currently in preview and is secheduled for release in November, 2025. +> +> * Add a package reference to the app for the [`Microsoft.EntityFrameworkCore.Design`](https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Design) NuGet package: +> +> ```dotnetcli +> dotnet add package Microsoft.EntityFrameworkCore.Design +> ``` +> +> Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: +> +> ```diff +> +> runtime; build; native; contentfiles; analyzers; buildtransitive +> all +> + true +> +> ``` +> +> The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The change to the package reference can be reverted in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). :::moniker-end From 666eb37ec2307c837dace27830e5f07bb191ce34 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Wed, 26 Feb 2025 14:21:43 -0500 Subject: [PATCH 2/4] Updates --- .../tutorials/movie-database-app/part-2.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md index 149d478b8a2b..bc07136b2d7d 100644 --- a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md +++ b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md @@ -145,25 +145,25 @@ dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore > > Adopt ***either*** of the following approaches: > -> * Use a .NET SDK for .NET 10 or later. .NET 10 is currently in preview and is secheduled for release in November, 2025. +> * Use a .NET SDK for [.NET 10](https://dotnet.microsoft.com/download/dotnet/10.0) or later. .NET 10 is currently in preview and is secheduled for release in November, 2025. If you obtain and use the .NET 10 SDK for this tutorial, you can leave the app targeting .NET 9. > > * Add a package reference to the app for the [`Microsoft.EntityFrameworkCore.Design`](https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Design) NuGet package: > -> ```dotnetcli -> dotnet add package Microsoft.EntityFrameworkCore.Design -> ``` +> ```dotnetcli +> dotnet add package Microsoft.EntityFrameworkCore.Design +> ``` > -> Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: +> Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: > -> ```diff -> -> runtime; build; native; contentfiles; analyzers; buildtransitive -> all -> + true -> -> ``` +> ```diff +> +> runtime; build; native; contentfiles; analyzers; buildtransitive +> all +> + true +> +> ``` > -> The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The change to the package reference can be reverted in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). +> The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The change to the package reference can be reverted in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). :::moniker-end From b88cb03f38dc6553a23e753a62c209884cd3c1f2 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Wed, 26 Feb 2025 14:27:01 -0500 Subject: [PATCH 3/4] Updates --- .../tutorials/movie-database-app/part-2.md | 91 ++++++------------- 1 file changed, 27 insertions(+), 64 deletions(-) diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md index bc07136b2d7d..9c3b37d64aa5 100644 --- a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md +++ b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md @@ -163,7 +163,7 @@ dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore > > ``` > -> The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The change to the package reference can be reverted in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). +> The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The entire package reference can be removed in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). :::moniker-end @@ -197,73 +197,36 @@ Paste all of the following commands at the prompt (`>`) of the command shell. W When you paste multiple commands, all of the commands execute except the last one. The last command doesn't execute until you press Enter on the keyboard. -:::moniker range=">= aspnetcore-10.0" - -```dotnetcli -dotnet tool install --global dotnet-aspnet-codegenerator -dotnet tool install --global dotnet-ef -dotnet add package Microsoft.EntityFrameworkCore.SQLite -dotnet add package Microsoft.VisualStudio.Web.CodeGeneration.Design -dotnet add package Microsoft.EntityFrameworkCore.SqlServer -dotnet add package Microsoft.EntityFrameworkCore.Tools -dotnet add package Microsoft.AspNetCore.Components.QuickGrid -dotnet add package Microsoft.AspNetCore.Components.QuickGrid.EntityFrameworkAdapter -dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore -``` - -> [!IMPORTANT] -> After the first eight commands execute, make sure that you press Enter on the keyboard to execute the last command. - -:::moniker-end - :::moniker range=">= aspnetcore-9.0 < aspnetcore-10.0" -```dotnetcli -dotnet tool install --global dotnet-aspnet-codegenerator -dotnet tool install --global dotnet-ef -dotnet add package Microsoft.EntityFrameworkCore.SQLite -dotnet add package Microsoft.VisualStudio.Web.CodeGeneration.Design -dotnet add package Microsoft.EntityFrameworkCore.SqlServer -dotnet add package Microsoft.EntityFrameworkCore.Tools -dotnet add package Microsoft.AspNetCore.Components.QuickGrid -dotnet add package Microsoft.AspNetCore.Components.QuickGrid.EntityFrameworkAdapter -dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore -dotnet add package Microsoft.EntityFrameworkCore.Design -``` - -> [!IMPORTANT] -> After the first nine commands execute, make sure that you press Enter on the keyboard to execute the last command. - -Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: - -```diff - - runtime; build; native; contentfiles; analyzers; buildtransitive - all -+ true - -``` - -The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The change to the package reference can be reverted in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). - -:::moniker-end - -:::moniker range="< aspnetcore-9.0" - -```dotnetcli -dotnet tool install --global dotnet-aspnet-codegenerator -dotnet tool install --global dotnet-ef -dotnet add package Microsoft.EntityFrameworkCore.SQLite -dotnet add package Microsoft.VisualStudio.Web.CodeGeneration.Design -dotnet add package Microsoft.EntityFrameworkCore.SqlServer -dotnet add package Microsoft.EntityFrameworkCore.Tools -dotnet add package Microsoft.AspNetCore.Components.QuickGrid -dotnet add package Microsoft.AspNetCore.Components.QuickGrid.EntityFrameworkAdapter -dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore -``` + > [!IMPORTANT] -> After the first eight commands execute, make sure that you press Enter on the keyboard to execute the last command. +> If using the .NET 9 SDK, a breaking change in EF Core tooling prevents scaffolding from executing with the following exception: +> +> > :::no-loc text="Could not load file or assembly 'Microsoft.EntityFrameworkCore.Design, Version=9.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified."::: +> +> Adopt ***either*** of the following approaches: +> +> * Use a .NET SDK for [.NET 10](https://dotnet.microsoft.com/download/dotnet/10.0) or later. .NET 10 is currently in preview and is secheduled for release in November, 2025. If you obtain and use the .NET 10 SDK for this tutorial, you can leave the app targeting .NET 9. +> +> * Add a package reference to the app for the [`Microsoft.EntityFrameworkCore.Design`](https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Design) NuGet package: +> +> ```dotnetcli +> dotnet add package Microsoft.EntityFrameworkCore.Design +> ``` +> +> Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: +> +> ```diff +> +> runtime; build; native; contentfiles; analyzers; buildtransitive +> all +> + true +> +> ``` +> +> The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The entire package reference can be removed in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). :::moniker-end From 5a97559abdeffc48dc2d1e4c1e0f918d90286721 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Wed, 26 Feb 2025 14:50:54 -0500 Subject: [PATCH 4/4] Updates --- .../tutorials/movie-database-app/part-2.md | 72 +++++++++---------- 1 file changed, 32 insertions(+), 40 deletions(-) diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md index 9c3b37d64aa5..0e1cef1a86f4 100644 --- a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md +++ b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md @@ -134,36 +134,32 @@ dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore > [!IMPORTANT] > After the first eight commands execute, make sure that you press Enter on the keyboard to execute the last command. -:::moniker range=">= aspnetcore-9.0 < aspnetcore-10.0" +:::moniker range=">= aspnetcore-9.0" - + > [!IMPORTANT] -> If using the .NET 9 SDK, a breaking change in EF Core tooling prevents scaffolding from executing with the following exception: +> A breaking change in EF Core tooling for .NET SDK 9.0.200 prevents scaffolding from executing with the following exception: > > > :::no-loc text="Could not load file or assembly 'Microsoft.EntityFrameworkCore.Design, Version=9.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified."::: > -> Adopt ***either*** of the following approaches: -> -> * Use a .NET SDK for [.NET 10](https://dotnet.microsoft.com/download/dotnet/10.0) or later. .NET 10 is currently in preview and is secheduled for release in November, 2025. If you obtain and use the .NET 10 SDK for this tutorial, you can leave the app targeting .NET 9. -> -> * Add a package reference to the app for the [`Microsoft.EntityFrameworkCore.Design`](https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Design) NuGet package: +> To resolve the error until the .NET SDK 9.0.300 is released, add a package reference to the app for the [`Microsoft.EntityFrameworkCore.Design`](https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Design) NuGet package: > -> ```dotnetcli -> dotnet add package Microsoft.EntityFrameworkCore.Design -> ``` +> ```dotnetcli +> dotnet add package Microsoft.EntityFrameworkCore.Design +> ``` > -> Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: +> Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: > -> ```diff -> -> runtime; build; native; contentfiles; analyzers; buildtransitive -> all -> + true -> -> ``` +> ```diff +> +> runtime; build; native; contentfiles; analyzers; buildtransitive +> all +> + true +> +> ``` > -> The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The entire package reference can be removed in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). +> The preceding changes are a workaround for a breaking change in .NET 9.0.200 EF Core tooling. This workaround won't be required for .NET SDK 9.0.300 or later, when the entire package reference can be removed from the app. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). :::moniker-end @@ -197,36 +193,32 @@ Paste all of the following commands at the prompt (`>`) of the command shell. W When you paste multiple commands, all of the commands execute except the last one. The last command doesn't execute until you press Enter on the keyboard. -:::moniker range=">= aspnetcore-9.0 < aspnetcore-10.0" +:::moniker range=">= aspnetcore-9.0" - + > [!IMPORTANT] -> If using the .NET 9 SDK, a breaking change in EF Core tooling prevents scaffolding from executing with the following exception: +> A breaking change in EF Core tooling for .NET SDK 9.0.200 prevents scaffolding from executing with the following exception: > > > :::no-loc text="Could not load file or assembly 'Microsoft.EntityFrameworkCore.Design, Version=9.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified."::: > -> Adopt ***either*** of the following approaches: -> -> * Use a .NET SDK for [.NET 10](https://dotnet.microsoft.com/download/dotnet/10.0) or later. .NET 10 is currently in preview and is secheduled for release in November, 2025. If you obtain and use the .NET 10 SDK for this tutorial, you can leave the app targeting .NET 9. -> -> * Add a package reference to the app for the [`Microsoft.EntityFrameworkCore.Design`](https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Design) NuGet package: +> To resolve the error until the .NET SDK 9.0.300 is released, add a package reference to the app for the [`Microsoft.EntityFrameworkCore.Design`](https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Design) NuGet package: > -> ```dotnetcli -> dotnet add package Microsoft.EntityFrameworkCore.Design -> ``` +> ```dotnetcli +> dotnet add package Microsoft.EntityFrameworkCore.Design +> ``` > -> Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: +> Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `true` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: > -> ```diff -> -> runtime; build; native; contentfiles; analyzers; buildtransitive -> all -> + true -> -> ``` +> ```diff +> +> runtime; build; native; contentfiles; analyzers; buildtransitive +> all +> + true +> +> ``` > -> The preceding update to the package reference is a workaround for a breaking change in .NET 9 EF Core tooling. The entire package reference can be removed in apps that are eventually updated to .NET 10 or later. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). +> The preceding changes are a workaround for a breaking change in .NET 9.0.200 EF Core tooling. This workaround won't be required for .NET SDK 9.0.300 or later, when the entire package reference can be removed from the app. For more information, see [Breaking changes in EF Core 9 (EF9)](/ef/core/what-is-new/ef-core-9.0/breaking-changes#microsoftentityframeworkcoredesign-not-found-when-using-ef-tools). :::moniker-end