diff --git a/aspnetcore/release-notes/aspnetcore-11.md b/aspnetcore/release-notes/aspnetcore-11.md index 0896a74c0657..a311cac83335 100644 --- a/aspnetcore/release-notes/aspnetcore-11.md +++ b/aspnetcore/release-notes/aspnetcore-11.md @@ -5,7 +5,7 @@ author: wadepickett description: Learn about the new features in ASP.NET Core in .NET 11. ms.author: wpickett ms.custom: mvc -ms.date: 12/04/2025 +ms.date: 03/10/2026 uid: aspnetcore-11 --- # What's new in ASP.NET Core in .NET 11 @@ -64,5 +64,5 @@ This section describes miscellaneous new features in .NET 11. ## Breaking changes -Use the articles in [Breaking changes in .NET]([/dotnet/core/compatibility/breaking-changes](https://learn.microsoft.com/dotnet/core/compatibility/breaking-changes)) to find breaking changes that might apply when upgrading an app to a newer version of .NET. +Use the articles in [Breaking changes in .NET](/dotnet/core/compatibility/breaking-changes) to find breaking changes that might apply when upgrading an app to a newer version of .NET. diff --git a/aspnetcore/release-notes/aspnetcore-11/includes/infer-passkey-display-name-preview2.md b/aspnetcore/release-notes/aspnetcore-11/includes/infer-passkey-display-name-preview2.md index e57fbc189ee6..ff93f731ddc7 100644 --- a/aspnetcore/release-notes/aspnetcore-11/includes/infer-passkey-display-name-preview2.md +++ b/aspnetcore/release-notes/aspnetcore-11/includes/infer-passkey-display-name-preview2.md @@ -2,4 +2,4 @@ ASP.NET Core Identity now automatically infers friendly display names for passkeys based on their AAGUID (Authenticator Attestation GUID). Built-in mappings are included for the most commonly used passkey authenticators, including Google Password Manager, iCloud Keychain, Windows Hello, 1Password, and Bitwarden. -For known authenticators, the name is automatically assigned without prompting the user. For unknown authenticators, the user is redirected to a rename page. Developers can extend the mappings by adding entries to the `PasskeyAuthenticators.cs` dictionary in their project. +For known authenticators, the name is automatically assigned without prompting the user. For unknown authenticators, the user is redirected to a rename page. Extend the mappings by adding entries to the `PasskeyAuthenticators` dictionary in the project. diff --git a/aspnetcore/release-notes/aspnetcore-11/includes/native-otel-tracing-preview2.md b/aspnetcore/release-notes/aspnetcore-11/includes/native-otel-tracing-preview2.md index 3336cc0ffe8d..5ce427b99fb9 100644 --- a/aspnetcore/release-notes/aspnetcore-11/includes/native-otel-tracing-preview2.md +++ b/aspnetcore/release-notes/aspnetcore-11/includes/native-otel-tracing-preview2.md @@ -11,6 +11,6 @@ builder.Services.AddOpenTelemetry() .AddConsoleExporter()); ``` -No additional instrumentation library (such as `OpenTelemetry.Instrumentation.AspNetCore`) is needed. The framework now directly populates semantic convention attributes like `http.request.method`, `url.path`, `http.response.status_code`, and `server.address` on the request activity. +No additional instrumentation library (such as `OpenTelemetry.Instrumentation.AspNetCore`) is needed. The framework now directly populates semantic convention attributes on the request activity, such as `http.request.method`, `url.path`, `http.response.status_code`, and `server.address`. If you don't want OpenTelemetry attributes added to the activity, you can turn it off by setting the `Microsoft.AspNetCore.Hosting.SuppressActivityOpenTelemetryData` AppContext switch to `true`. diff --git a/aspnetcore/release-notes/aspnetcore-11/includes/openapi-3-2-support-preview2.md b/aspnetcore/release-notes/aspnetcore-11/includes/openapi-3-2-support-preview2.md index df5a1711d2f1..2efae69a4664 100644 --- a/aspnetcore/release-notes/aspnetcore-11/includes/openapi-3-2-support-preview2.md +++ b/aspnetcore/release-notes/aspnetcore-11/includes/openapi-3-2-support-preview2.md @@ -1,8 +1,8 @@ ### OpenAPI 3.2.0 support (Breaking Change) -`Microsoft.AspNetCore.OpenApi` now supports OpenAPI 3.2.0 through an updated dependency on `Microsoft.OpenApi` 3.3.1. This update includes breaking changes from the underlying library — see the [Microsoft.OpenApi upgrade guide](https://github.com/microsoft/OpenAPI.NET/blob/main/docs/upgrade-guide-3.md) for details. +`Microsoft.AspNetCore.OpenApi` now supports OpenAPI 3.2.0 through an updated dependency on `Microsoft.OpenApi` 3.3.1. This update includes breaking changes from the underlying library. For more information, see the [Microsoft.OpenApi upgrade guide](https://github.com/microsoft/OpenAPI.NET/blob/main/docs/upgrade-guide-3.md). -To generate an OpenAPI 3.2.0 document, specify the version when calling `AddOpenApi()`: +To generate an OpenAPI 3.2.0 document, specify the version when calling : ```csharp builder.Services.AddOpenApi(options => @@ -11,6 +11,6 @@ builder.Services.AddOpenApi(options => }); ``` -Subsequent updates will take advantage of new capabilities in the 3.2.0 specification, such as item schema support for streaming events. +Subsequent updates take advantage of new capabilities in the 3.2.0 specification, such as item schema support for streaming events. Thank you [@baywet](https://github.com/baywet) for this contribution! diff --git a/aspnetcore/release-notes/aspnetcore-11/includes/performance-improvements-preview2.md b/aspnetcore/release-notes/aspnetcore-11/includes/performance-improvements-preview2.md index bb888cc84119..6d73f8724472 100644 --- a/aspnetcore/release-notes/aspnetcore-11/includes/performance-improvements-preview2.md +++ b/aspnetcore/release-notes/aspnetcore-11/includes/performance-improvements-preview2.md @@ -1,5 +1,5 @@ ### Performance improvements -Kestrel's HTTP/1.1 request parser now uses a non-throwing code path for handling malformed requests. Instead of throwing `BadHttpRequestException` on every parse failure, the parser returns a result struct indicating success, incomplete, or error states. In scenarios with many malformed requests — such as port scanning, malicious traffic, or misconfigured clients — this eliminates expensive exception handling overhead and improves throughput by up to 20-40%. There's no impact on valid request processing. +Kestrel's HTTP/1.1 request parser now uses a non-throwing code path for handling malformed requests. Instead of throwing on every parse failure, the parser returns a result struct indicating success, incomplete, or error states. In scenarios with many malformed requests — such as port scanning, malicious traffic, or misconfigured clients — this eliminates expensive exception handling overhead and improves throughput by up to 20-40%. There's no impact on valid request processing. The HTTP logging middleware now pools its `ResponseBufferingStream` instances, reducing per-request allocations when response body logging or interceptors are enabled.