Merge pull request #35463 from dotnet/main

Author: guardrex

aspnetcore/blazor/tutorials/movie-database-app/part-2.md

@@ -134,32 +134,18 @@ dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore
 > [!IMPORTANT]
 > After the first eight commands execute, make sure that you press <kbd>Enter</kbd> on the keyboard to execute the last command.
 
-:::moniker range=">= aspnetcore-9.0"
+:::moniker range=">= aspnetcore-9.0 < aspnetcore-10.0"
 
-<!-- UPDATE 10.0 - Remove this when the 9.0.300 SDK lands. -->
+<!-- UPDATE 10.0 - Remove at 10.0 GA -->
 
 > [!IMPORTANT]
-> A breaking change in EF Core tooling for .NET SDK 9.0.200 prevents scaffolding from executing with the following exception:
+> A breaking change in EF Core tooling for .NET SDK 9.0.200 prevented 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.":::
 > 
-> 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
-> ```
-> 
-> Open the app's project file (`BlazorWebAppMovies.csproj`). Mark the `Microsoft.EntityFrameworkCore.Design` assembly reference as publishable by adding `<Publish>true</Publish>` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: 
+> To resolve the error, upgrade to a .NET SDK of 9.0.300 or later.
 >
-> ```diff
-> <PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="{VERSION}">
->   <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
->   <PrivateAssets>all</PrivateAssets>
-> + <Publish>true</Publish>
-> </PackageReference>
->  ```
->
-> 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).
+> 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
 
@@ -205,32 +191,20 @@ dotnet add package Microsoft.AspNetCore.Components.QuickGrid.EntityFrameworkAdap
 dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore
 ```
 
-:::moniker range=">= aspnetcore-9.0"
+:::moniker range=">= aspnetcore-9.0 < aspnetcore-10.0"
 
-<!-- UPDATE 10.0 - Remove this when the 9.0.300 SDK lands. -->
+<!-- UPDATE 10.0 - Remove at 10.0 GA -->
 
 > [!IMPORTANT]
-> A breaking change in EF Core tooling for .NET SDK 9.0.200 prevents scaffolding from executing with the following exception:
+> A breaking change in EF Core tooling for .NET SDK 9.0.200 prevented 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.":::
 > 
-> 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:
+> To resolve the error, upgrade to a .NET SDK of 9.0.300 or later.
 >
-> ```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 `<Publish>true</Publish>` to the package reference. In the following example, the `{VERSION}` placeholder is the package's version and remains unchanged: 
->
-> ```diff
-> <PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="{VERSION}">
->   <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
->   <PrivateAssets>all</PrivateAssets>
-> + <Publish>true</Publish>
-> </PackageReference>
->  ```
->
-> 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).
+> 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-end
 

aspnetcore/release-notes/aspnetcore-10.0.md

@@ -39,6 +39,8 @@ This section describes new features for minimal APIs.
 
 [!INCLUDE[](~/release-notes/aspnetcore-10/includes/ValidationSupportMinAPI.md)]
 
+[!INCLUDE[](~/release-notes/aspnetcore-10/includes/MinimalAPIValidationRecordTypes.md)]
+
 [!INCLUDE[](~/release-notes/aspnetcore-10/includes/sse.md)]
 
 ## OpenAPI
@@ -59,6 +61,8 @@ This section describes new features for OpenAPI.
 
 [!INCLUDE[](~/release-notes/aspnetcore-10/includes/OpenApiSchemasInTransformers.md)]
 
+[!INCLUDE[](~/release-notes/aspnetcore-10/includes/OpenApiNetUpdatePrev17.md)]
+
 ### Authentication and authorization
 
 This section describes new features for authentication and authorization.

aspnetcore/release-notes/aspnetcore-10/includes/MinimalAPIValidationRecordTypes.md

@@ -1,7 +1,21 @@
-### Improvements to Minimal APIs Validation
-
+#### Validation with record types
 <!-- https://github.com/dotnet/aspnetcore/pull/61193 -->
 <!-- https://github.com/dotnet/aspnetcore/pull/61402 -->
-Beginning in Preview 4, ASP.NET Core supports validation on record types. With this enhancement,
-inputs to API endpoints defined using `record` types are now validated automatically, in the same way as
-class types.
+
+Minimal APIs also support validation with C# record types. Record types can be validated using attributes from the <xref:System.ComponentModel.DataAnnotations?displayProperty=fullName> namespace, similar to classes. For example:
+
+```csharp
+public record Product(
+    [Required] string Name,
+    [Range(1, 1000)] int Quantity);
+```
+
+When using record types as parameters in Minimal API endpoints, validation attributes are automatically applied in the same way as class types:
+
+```csharp
+app.MapPost("/products", (Product product) =>
+{
+    // Endpoint logic here
+    return TypedResults.Ok(product);
+});
+```

aspnetcore/release-notes/aspnetcore-10/includes/OpenApiNetUpdatePrev17.md

@@ -0,0 +1,6 @@
+### OpenAPI.NET updated to Preview.17
+
+The OpenAPI.NET library used in ASP.NET Core OpenAPI document generation was upgraded to [v2.0.0-preview17](https://www.nuget.org/packages/Microsoft.OpenApi/2.0.0-preview.17). This version includes a number of bug fixes and improvements and also introduces some breaking changes. The breaking changes should only affect users that use document, operation, or schema transformers. Breaking changes in this iteration that may affect developers include the following:
+
+* [Ephemeral object properties are now in Metadata](https://github.com/microsoft/OpenAPI.NET/blob/main/docs/upgrade-guide-2.md#ephemeral-object-properties-are-now-in-metadata)
+* [Use HTTP Method Object Instead of Enum](https://github.com/microsoft/OpenAPI.NET/blob/main/docs/upgrade-guide-2.md#use-http-method-object-instead-of-enum)