diff --git a/release-notes/11.0/preview/rc1/aspnetcore.md b/release-notes/11.0/preview/rc1/aspnetcore.md new file mode 100644 index 0000000000..9ce3df72f8 --- /dev/null +++ b/release-notes/11.0/preview/rc1/aspnetcore.md @@ -0,0 +1,496 @@ +# ASP.NET Core in .NET 11 RC 1 - Release Notes + +.NET 11 RC 1 includes new ASP.NET Core features and improvements: + +- [SignalR authentication refresh APIs are finalized](#signalr-authentication-refresh-apis-are-finalized) +- [SignalR TypeScript client supports authentication refresh](#signalr-typescript-client-supports-authentication-refresh) +- [Blazor Server circuits update after authentication refresh](#blazor-server-circuits-update-after-authentication-refresh) +- [OpenAPI reflects obsolete APIs](#openapi-reflects-obsolete-apis) +- [Validation localization uses message conventions](#validation-localization-uses-message-conventions) +- [Blazor browser options are finalized](#blazor-browser-options-are-finalized) +- [Select an environment for build-time OpenAPI](#select-an-environment-for-build-time-openapi) +- [Experimental Device Bound Session Credentials support](#experimental-device-bound-session-credentials-support) +- [Experimental Blazor AI components for agentic user interfaces](#experimental-blazor-ai-components-for-agentic-user-interfaces) +- [Experimental DirectTls transport](#experimental-directtls-transport) +- [Breaking changes](#breaking-changes) +- [Bug fixes](#bug-fixes) +- [Community contributors](#community-contributors) + +ASP.NET Core updates in .NET 11: + +- [What's new in ASP.NET Core in .NET 11](https://learn.microsoft.com/aspnet/core/release-notes/aspnetcore-11) + +## SignalR authentication refresh APIs are finalized + +[.NET 11 Preview 6 introduced authentication refresh](../preview6/aspnetcore.md#signalr-authentication-refresh) so a SignalR client can replace an expiring access token without dropping its connection. RC 1 finalizes the server and .NET client API shapes ([dotnet/aspnetcore #68702](https://github.com/dotnet/aspnetcore/pull/68702)). + +When upgrading from Preview 7: + +- In the .NET client, move the `OnAuthenticationRefreshed` and `OnAuthenticationRefreshFailed` callbacks from `AuthenticationRefreshOptions` to the `HubConnection.AuthenticationRefreshed` and `HubConnection.AuthenticationRefreshFailed` events. +- Update references to `Microsoft.AspNetCore.Http.Connections.AuthenticationRefreshContext` to use `Microsoft.AspNetCore.Connections.Features.AuthenticationRefreshContext`. +- Replace `IConnectionUserRefreshFeature` with `IConnectionAuthenticationRefreshFeature` if your transport integration uses the lower-level connection feature. + +The server opts in for each hub and can inspect or reject a refreshed identity: + +```csharp +using System.Security.Claims; + +app.MapHub("/clock", options => +{ + options.EnableAuthenticationRefresh = true; + options.CloseOnAuthenticationExpiration = true; + options.OnAuthenticationRefresh = context => + { + var previousSubject = context.PreviousUser.FindFirstValue("sub") + ?? context.PreviousUser.FindFirstValue(ClaimTypes.NameIdentifier); + var newSubject = context.NewUser.FindFirstValue("sub") + ?? context.NewUser.FindFirstValue(ClaimTypes.NameIdentifier); + + return Task.FromResult( + previousSubject is not null && + string.Equals(previousSubject, newSubject, StringComparison.Ordinal)); + }; +}); +``` + +The .NET client can refresh automatically before expiration or immediately after the app obtains new claims. Refresh notifications are events on `HubConnection`: + +```csharp +await using var connection = new HubConnectionBuilder() + .WithUrl(serverUrl, options => + options.AccessTokenProvider = GetAccessTokenAsync) + .WithAuthenticationRefresh(options => + { + options.EnableAutoRefresh = true; + options.RefreshBeforeExpiration = TimeSpan.FromMinutes(2); + }) + .Build(); + +connection.AuthenticationRefreshed += context => +{ + Console.WriteLine($"New token lifetime: {context.NewTokenLifetime}"); + return Task.CompletedTask; +}; + +connection.AuthenticationRefreshFailed += context => +{ + Console.WriteLine(context.Exception.Message); + return Task.CompletedTask; +}; + +await connection.StartAsync(); + +// Refresh immediately after acquiring a token with updated claims. +await connection.RefreshAuthenticationAsync(); +``` + +## SignalR TypeScript client supports authentication refresh + +The SignalR TypeScript client now supports refreshing an access token without reconnecting ([dotnet/aspnetcore #67964](https://github.com/dotnet/aspnetcore/pull/67964), [dotnet/aspnetcore #68702](https://github.com/dotnet/aspnetcore/pull/68702)). It can schedule a refresh from the token lifetime reported by the server or refresh immediately after the application obtains updated claims. + +Configure automatic refresh with `withAuthenticationRefresh`, register success and failure handlers on the built connection, and call `refreshAuthentication` to request a manual refresh: + +```typescript +const connection = new signalR.HubConnectionBuilder() + .withUrl("/clock", { accessTokenFactory: getAccessToken }) + .withAuthenticationRefresh({ + enableAutoRefresh: true, + refreshBeforeExpirationInMilliseconds: 120_000, + }) + .build(); + +connection.onAuthenticationRefreshed((context) => { + console.log(`New token lifetime: ${context.newTokenLifetimeInSeconds}`); +}); + +connection.onAuthenticationRefreshFailed((context) => { + console.error(context.error); +}); + +await connection.start(); + +// Refresh immediately after acquiring a token with updated claims. +await connection.refreshAuthentication(); +``` + +## Blazor Server circuits update after authentication refresh + +Interactive Server components can now receive the refreshed `ClaimsPrincipal` without reconnecting the circuit ([dotnet/aspnetcore #68221](https://github.com/dotnet/aspnetcore/pull/68221)). The Blazor component hub and client enable authentication refresh automatically, so no additional configuration is required ([dotnet/aspnetcore #68593](https://github.com/dotnet/aspnetcore/pull/68593)). + +After the connection refreshes its authentication, Blazor updates the authentication state and raises `AuthenticationStateChanged`. Components that consume `AuthenticationStateProvider`, including `AuthorizeView`, re-render using the refreshed identity and claims. This behavior is useful when a user's roles or permissions change during an active circuit, or when a component needs to reload user-specific content after claims are refreshed. The UI can reflect the new authentication state without forcing the user to reconnect or reload the page. + +## OpenAPI reflects obsolete APIs + +ASP.NET Core OpenAPI generation now maps `[Obsolete]` to `deprecated: true` automatically for operations, schema types, and schema properties ([dotnet/aspnetcore #66355](https://github.com/dotnet/aspnetcore/pull/66355)). API clients and documentation tools can therefore surface the same deprecation information as .NET callers without a custom OpenAPI transformer. + +```csharp +app.MapGet("/catalog/{id}", GetCatalogItem); + +#pragma warning disable CS0618 // This example intentionally declares and maps obsolete APIs. +app.MapGet("/catalog/legacy/{id}", GetLegacyCatalogItem); + +[Obsolete("Use /catalog/{id}.")] +static LegacyCatalogItem GetLegacyCatalogItem(int id) => + new(id, $"Product {id}", $"SKU-{id:D4}"); + +static CatalogItem GetCatalogItem(int id) => + new(id, $"Product {id}", $"SKU-{id:D4}"); + +public sealed record CatalogItem( + int Id, + string Name, + string StockKeepingUnit); + +[Obsolete("Use CatalogItem.")] +public sealed record LegacyCatalogItem( + int Id, + string Name, + [property: Obsolete("Use StockKeepingUnit.")] string Sku); + +#pragma warning restore CS0618 +``` + +The legacy operation, its response schema, and the `Sku` property are marked deprecated in the generated document: + +```json +{ + "paths": { + "/catalog/legacy/{id}": { + "get": { + "deprecated": true + } + } + }, + "components": { + "schemas": { + "LegacyCatalogItem": { + "deprecated": true, + "properties": { + "sku": { + "deprecated": true + } + } + } + } + } +} +``` + +An `IOpenApiOperationTransformer` or `IOpenApiSchemaTransformer` can override the generated value for a specific API. + +Thank you [@fickleEfrit](https://github.com/fickleEfrit) for this contribution! + +## Validation localization uses message conventions + +[Preview 7 integrated localization directly into `Microsoft.Extensions.Validation`](../preview7/aspnetcore.md#validation-localization-is-built-in). RC 1 replaces the preview-only `MessageKeyProvider` API with built-in resource-name conventions ([dotnet/aspnetcore #68202](https://github.com/dotnet/aspnetcore/pull/68202)). + +When upgrading from Preview 7, remove assignments to `ValidationOptions.MessageKeyProvider` and rename the corresponding resource keys to match one of the built-in conventions below. The `ValidationMessageKeyContext` type was also removed because custom key providers are no longer used. + +When a validation attribute doesn't specify `ErrorMessage`, localization tries these keys from most to least specific: + +1. `{DeclaringType}_{MemberName}_{AttributeType}_Error` +2. `{DeclaringType}_{AttributeType}_Error` +3. `{AttributeType}_Error` + +For example, this model can use `RegistrationModel_Username_RequiredAttribute_Error`, `RegistrationModel_RequiredAttribute_Error`, or the shared `RequiredAttribute_Error` resource: + +```csharp +using System.ComponentModel.DataAnnotations; +using Microsoft.Extensions.Validation; + +builder.Services.AddLocalization(); +builder.Services.AddValidation(options => +{ + options.LocalizerProvider = (_, factory) => + factory.Create(typeof(MyApp.Resources.ValidationMessages)); +}); + +[ValidatableType] +public sealed class RegistrationModel +{ + [Required] + [StringLength(20, MinimumLength = 4)] + [Display(Name = "Username")] + public string Username { get; set; } = ""; +} + +namespace MyApp.Resources +{ + // Resources/ValidationMessages.resx uses this type's namespace and name. + public sealed class ValidationMessages + { + } +} +``` + +An explicit `ErrorMessage` remains the first resource key to try. If no resource resolves, validation falls back to the non-localized message. The same conventions apply to Blazor static SSR client validation. + +## Blazor browser options are finalized + +The [server-to-client configuration API introduced in Preview 6](../preview6/aspnetcore.md#configure-blazor-client-behavior-from-the-server) now uses its final RC 1 names ([dotnet/aspnetcore #67918](https://github.com/dotnet/aspnetcore/pull/67918)). + +When upgrading from Preview 7, update the following APIs: + +| Preview 7 | RC 1 | +| --------------------------------- | ----------------------------------------------- | +| `BrowserOptions.Server` | `BrowserOptions.InteractiveServer` | +| `BrowserOptions.Ssr` | `BrowserOptions.StaticServer` | +| `BrowserOptions.WebAssembly` | `BrowserOptions.InteractiveWebAssembly` | +| `SsrBrowserOptions` | `StaticServerBrowserOptions` | +| `WebAssemblyBrowserOptions` | `InteractiveWebAssemblyBrowserOptions` | +| `httpContext.GetBrowserOptions()` | `BrowserOptions.GetBrowserOptions(httpContext)` | + +Configure browser startup behavior in C# with `WithBrowserOptions`: + +```csharp +app.MapRazorComponents() + .AddInteractiveServerRenderMode() + .WithBrowserOptions(options => + { + options.LogLevel = LogLevel.Information; + options.InteractiveServer.ReconnectionMaxRetries = 10; + options.InteractiveServer.ReconnectionRetryInterval = + TimeSpan.FromSeconds(1.5); + options.StaticServer.PreserveDom = true; + options.InteractiveWebAssembly.EnvironmentVariables["OTEL_ENDPOINT"] = + "https://localhost:4318"; + }); +``` + +The finalized properties are `InteractiveServer`, `StaticServer`, and `InteractiveWebAssembly`. Server code can read the resolved configuration with `BrowserOptions.GetBrowserOptions(HttpContext)`. + +## Select an environment for build-time OpenAPI + +Build-time OpenAPI generation can now run the app under a specified hosting environment ([dotnet/aspnetcore #63856](https://github.com/dotnet/aspnetcore/pull/63856)). For projects that use the `Microsoft.Extensions.ApiDescription.Server` package to generate OpenAPI documents at build time, set `OpenApiGenerationEnvironment` when environment-specific services, endpoints, or transformers affect the generated document: + +```xml + + true + Development + +``` + +The value is passed to the application host in the same role as `ASPNETCORE_ENVIRONMENT` or `DOTNET_ENVIRONMENT`. + +Thank you [@ldsenow](https://github.com/ldsenow) for this contribution! + +## Experimental Device Bound Session Credentials support + +> [!IMPORTANT] +> The `Microsoft.AspNetCore.Authentication.DeviceBoundSessions` package is experimental and will remain prerelease throughout .NET 11 and until the specification stabilizes. For .NET 11 RC1, use version `0.11.0-rc.1.26427.112` of the package. + +The [DBSC specification](https://w3c.github.io/webappsec-dbsc/) defines a protocol that binds session refresh to a private key held by the browser. The app issues a short-lived session cookie, and the browser must provide a signed proof of possession to refresh it. A copied session cookie might remain usable until it expires, but an attacker without the device key can't use it to extend the session. + +ASP.NET Core in .NET 11 RC1 adds an experimental server-side DBSC implementation in the `Microsoft.AspNetCore.Authentication.DeviceBoundSessions` package ([dotnet/aspnetcore #67388](https://github.com/dotnet/aspnetcore/pull/67388)). The authentication component layers over an existing cookie authentication scheme and manages the registration and refresh endpoints, a path-scoped refresh cookie, and the short-lived session cookie. + +After adding the `Microsoft.AspNetCore.Authentication.DeviceBoundSessions` package, configure DBSC over an existing cookie authentication scheme: + +```csharp +builder.Services + .AddAuthentication("Application") + .AddCookie("Application") + .AddDeviceBoundSession("Application", options => + { + options.ShortLivedCookieExpiration = TimeSpan.FromMinutes(10); + }); +``` + +Browser support currently requires an experimental DBSC implementation. See [Chrome's DBSC documentation](https://developer.chrome.com/docs/web-platform/device-bound-session-credentials) for implementation and enablement details. + +## Experimental Blazor AI components for agentic user interfaces + +Modern AI apps increasingly provide rich interactions with agents. A complete agentic user interface may need to stream ongoing work, visualize agent reasoning and progress, request approval before tools act, accept multimodal input, and synchronize state between the app and the agent. The Blazor AI components are designed to provide building blocks for creating these experiences using Blazor's component model. + +.NET 11 RC1 includes an initial set of Blazor AI components focused on streaming chat and rich-text rendering. + +> [!IMPORTANT] +> The `Microsoft.AspNetCore.Components.AI` package is experimental and will remain prerelease throughout .NET 11. For .NET 11 RC1, use version `11.0.0-preview.7.26427.112` of the package. + +### Stream conversations into Blazor components + +The initial streaming chat support ([dotnet/aspnetcore #68323](https://github.com/dotnet/aspnetcore/pull/68323)) is provider- and protocol-neutral. Apps supply an `IChatClient` from `Microsoft.Extensions.AI`, and `UIAgent` converts its streaming responses into observable content blocks that the UI can render as they arrive. `UIAgent` also retains the message history for subsequent turns. + +`ChatPage` is a complete chat shell that combines three lower-level components: + +- `AgentBoundary` creates and cascades the conversation state. +- `MessageList` renders each turn as it streams and provides default typing, error, and retry UI. +- `MessageInput` sends messages from a text area and disables input while a response is streaming. + +The following component creates a `UIAgent` over an app-provided `IChatClient` and renders the conversation with `ChatPage`: + +```razor +@using Microsoft.AspNetCore.Components.AI +@using Microsoft.Extensions.AI +@rendermode InteractiveServer +@implements IDisposable +@inject IChatClient ChatClient + + + +

Ask the agent a question.

+ + + +@code { + private UIAgent _agent = default!; + + protected override void OnInitialized() + { + _agent = new UIAgent(ChatClient); + } + + public void Dispose() => _agent.Dispose(); +} +``` + +Include the component styles in `App.razor`: + +```razor + +``` + +![Blazor AI chat interface showing a conversation with a travel planning agent](media/blazor-ai-chat.png) + +Because `UIAgent` accepts any `IChatClient`, it can also use an [`AGUIChatClient`](https://docs.ag-ui.com/sdk/dotnet/client/chat-client) to connect the Blazor UI to a remote agent over the Agent User Interaction Protocol (AG-UI): + +```csharp +using AGUI.Client; +using Microsoft.Extensions.AI; + +builder.Services.AddHttpClient(httpClient => + new AGUIChatClient(new(httpClient, "https://api.example.com/agent"))); +``` + +`AGUIChatClient` streams AG-UI events as `ChatResponseUpdate` values. The RC1 components render the conversational content from these updates, while apps can use the additional AG-UI event information to build richer agentic interactions. + +### Render rich text + +The rich-text support ([dotnet/aspnetcore #68324](https://github.com/dotnet/aspnetcore/pull/68324)) lets an `IChatClient` provide complete structured snapshots using `RichTextContent` and `RichTextNode` values. The built-in renderer supports headings, paragraphs, emphasis, links, lists, code blocks, tables, and other presentation elements. Plain `TextContent` continues to render as paragraphs. + +![Blazor AI chat interface rendering a heading, emphasized text, a list, a quote, a code block, and a table](media/blazor-ai-rich-text.png) + +Components.AI doesn't prescribe a source format or parser. Apps can map a parser's syntax tree into `RichTextNode` values to use the built-in renderer, or register a custom `BlockRenderer`. The following example composes `MessageList` and `MessageInput` directly and uses the community [Markdig](https://www.nuget.org/packages/Markdig) library to render Markdown. Because the generated HTML is rendered as markup, the example also sanitizes it with [HtmlSanitizer](https://www.nuget.org/packages/HtmlSanitizer): + +```razor +@using Ganss.Xss +@using Markdig +@using Microsoft.AspNetCore.Components.AI +@using Microsoft.Extensions.AI +@rendermode InteractiveServer +@implements IDisposable +@inject IChatClient ChatClient + + + + +

Ask the agent a question.

+ + + + @RenderMarkdown(block.RawText) + + + + + + +@code { + private static readonly MarkdownPipeline MarkdownPipeline = + new MarkdownPipelineBuilder() + .UseAdvancedExtensions() + .DisableHtml() + .Build(); + private static readonly HtmlSanitizer HtmlSanitizer = new(); + private UIAgent _agent = default!; + + protected override void OnInitialized() + { + _agent = new UIAgent(ChatClient); + } + + private static MarkupString RenderMarkdown(string markdown) + { + var html = Markdown.ToHtml(markdown, MarkdownPipeline); + return new MarkupString(HtmlSanitizer.Sanitize(html)); + } + + public void Dispose() => _agent.Dispose(); +} +``` + +## Experimental DirectTls transport + +> [!WARNING] +> DirectTls is experimental in .NET 11 and produces diagnostic `ASPNETCORE_DIRECTTLS_001`. + +**DirectTls** is an opt-in Kestrel transport for Linux that terminates TLS directly on the connection's socket by using the runtime's low-level TLS APIs ([dotnet/aspnetcore #67912](https://github.com/dotnet/aspnetcore/pull/67912)). It binds OpenSSL to the socket file descriptor instead of using `SslStream`, avoiding an intermediate managed copy on the TLS data path. The transport is being explored for connection-dense and handshake-heavy workloads where those copies and allocations can be significant. + +DirectTls ships as the standalone `Microsoft.AspNetCore.Server.Kestrel.Transport.DirectTls` package and requires OpenSSL on the host. After adding a reference to the package, call `UseDirectTls()` to register the transport and select it for a specific endpoint. The following example assumes that `certificate` is an `X509Certificate2` loaded from the app's secure certificate configuration: + +```csharp +using System.Net; +using Microsoft.AspNetCore.Server.Kestrel.Core; +using Microsoft.AspNetCore.Server.Kestrel.Transport.DirectTls; + +#pragma warning disable ASPNETCORE_DIRECTTLS_001 // DirectTls is experimental. + +builder.WebHost.UseKestrel(); +builder.WebHost.UseDirectTls(); +builder.WebHost.ConfigureKestrel(options => +{ + var endpoint = new DirectTlsEndpoint(IPAddress.Any, 5001); + endpoint.Options.ServerCertificate = certificate; + options.Listen(endpoint); +}); +``` + +Only endpoints configured with `DirectTlsEndpoint` use DirectTls. Other endpoints continue to use the default sockets transport and the standard Kestrel TLS implementation. + +## Breaking changes + +### Preview-only insecure chunked parsing switch removed + +The `Microsoft.AspNetCore.Server.Kestrel.InsecureChunkedParsing` AppContext switch has been removed ([dotnet/aspnetcore #68553](https://github.com/dotnet/aspnetcore/pull/68553)). The switch was introduced during .NET 11 previews but wasn't intended to be part of .NET 11. Remove any call that enables the switch; there is no replacement, and Kestrel always uses secure chunked-request parsing. + +### Bootstrap 4 Identity UI is obsolete + +Projects that set `IdentityUIFrameworkVersion` to `Bootstrap4` now receive an MSBuild warning ([dotnet/aspnetcore #68575](https://github.com/dotnet/aspnetcore/pull/68575)). Change the value to `Bootstrap5`, or remove the property to use the default. Bootstrap 5 remains the supported Identity UI framework selection. + + + +## Bug fixes + +- **Blazor** + - [Fixed persisted component state for re-executed endpoints (dotnet/aspnetcore #68032)](https://github.com/dotnet/aspnetcore/pull/68032) + - [Fixed persisted component state being dropped during enhanced navigation (dotnet/aspnetcore #68088)](https://github.com/dotnet/aspnetcore/pull/68088) + - [Fixed `InputNumber` validation for floating-point values in scientific notation (dotnet/aspnetcore #67988)](https://github.com/dotnet/aspnetcore/pull/67988) + - [Fixed `Virtualize` scroll jumps caused by competing native and JavaScript anchoring (dotnet/aspnetcore #67934)](https://github.com/dotnet/aspnetcore/pull/67934) + - [Fixed `QuickGrid` viewport drift when prepending asynchronously loaded items in end-anchor mode (dotnet/aspnetcore #67938)](https://github.com/dotnet/aspnetcore/pull/67938) +- **Data Protection** + - [Fixed thread-pool starvation when `KeyRingProvider` performs a forced refresh (dotnet/aspnetcore #67986)](https://github.com/dotnet/aspnetcore/pull/67986) +- **Hosting** + - [Fixed an IIS application shutdown hang when preload is enabled (dotnet/aspnetcore #65733)](https://github.com/dotnet/aspnetcore/pull/65733) +- **OpenAPI** + - [Fixed nullability for nullable get-only and constructor-bound properties (dotnet/aspnetcore #68116)](https://github.com/dotnet/aspnetcore/pull/68116) +- **SignalR** + - [Hardened parsing of the `negotiateVersion` query value (dotnet/aspnetcore #67908)](https://github.com/dotnet/aspnetcore/pull/67908) + - [Hardened stateful reconnect handling (dotnet/aspnetcore #67409)](https://github.com/dotnet/aspnetcore/pull/67409) + +## Community contributors + +Thank you contributors! ❤️ + +- [@AbdelrahmanHassan131](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3AAbdelrahmanHassan131+milestone%3A11.0-rc1) +- [@akshay-zz](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3Aakshay-zz+milestone%3A11.0-rc1) +- [@aw0lid](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3Aaw0lid+milestone%3A11.0-rc1) +- [@fickleEfrit](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3AfickleEfrit+milestone%3A11.0-rc1) +- [@GrantTotinov](https://github.com/dotnet/aspnetcore/pull/67539) +- [@hishamco](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3Ahishamco+milestone%3A11.0-rc1) +- [@khellang](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3Akhellang+milestone%3A11.0-rc1) +- [@ldsenow](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3Aldsenow+milestone%3A11.0-rc1) +- [@PreethikaSelvam](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3APreethikaSelvam+milestone%3A11.0-rc1) +- [@surya3655](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3Asurya3655+milestone%3A11.0-rc1) +- [@vendasankarsf3945](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3Avendasankarsf3945+milestone%3A11.0-rc1) +- [@Yuvan111](https://github.com/dotnet/aspnetcore/pulls?q=is%3Apr+is%3Amerged+author%3AYuvan111+milestone%3A11.0-rc1) diff --git a/release-notes/11.0/preview/rc1/media/blazor-ai-chat.png b/release-notes/11.0/preview/rc1/media/blazor-ai-chat.png new file mode 100644 index 0000000000..6fcd86c35c Binary files /dev/null and b/release-notes/11.0/preview/rc1/media/blazor-ai-chat.png differ diff --git a/release-notes/11.0/preview/rc1/media/blazor-ai-rich-text.png b/release-notes/11.0/preview/rc1/media/blazor-ai-rich-text.png new file mode 100644 index 0000000000..9d0f84f9f0 Binary files /dev/null and b/release-notes/11.0/preview/rc1/media/blazor-ai-rich-text.png differ