Merge pull request #36790 from dotnet/main

Merge to Live

Author: wadepickett

aspnetcore/blazor/fundamentals/signalr.md

@@ -1799,6 +1799,76 @@ protected override async Task OnInitializedAsync()
 
 In the preceding code, `NavManager` is a <xref:Microsoft.AspNetCore.Components.NavigationManager>, and `AuthenticationStateProvider` is an <xref:Microsoft.AspNetCore.Components.Authorization.AuthenticationStateProvider> service instance ([`AuthenticationStateProvider` documentation](xref:blazor/security/authentication-state)).
 
+## Configure the hub URL endpoint for a loopback connection
+
+*This section only applies to server-side Blazor apps.*
+
+If HTTP requests in a server-side Blazor app are failing to connect to itself when using <xref:Microsoft.AspNetCore.Components.NavigationManager.ToAbsoluteUri%2A?displayProperty=nameWithType>, you might have a load balancer or proxy that isn't expecting requests from the backend server. In this scenario, you can try to change the hub URL that the client is using to connect directly to the backend server.
+
+The following example:
+
+* Configures the hub URL using <xref:System.UriBuilder> and passes it to <xref:Microsoft.AspNetCore.SignalR.Client.HubConnectionBuilderHttpExtensions.WithUrl%2A>.
+* Sets the URI based on the server's address (<xref:Microsoft.AspNetCore.Hosting.Server.Features.IServerAddressesFeature>) and machine name (<xref:System.Environment.MachineName%2A>).
+
+```razor
+@using System.Net
+@using System.Net.Sockets
+@using Microsoft.AspNetCore.Hosting.Server
+@using Microsoft.AspNetCore.Hosting.Server.Features
+@using Microsoft.AspNetCore.SignalR.Client
+@inject IHostEnvironment Environment
+@inject IServer Server
+
+...
+
+@code {
+    private HubConnection? hubConnection;
+
+    protected override async Task OnInitializedAsync()
+    {
+        var serverAddress = Server.Features
+           .Get<IServerAddressesFeature>()?
+           .Addresses
+           .FirstOrDefault(a => a.StartsWith("http://") || a.StartsWith("https://"));
+
+        if (serverAddress is null)
+        {
+            throw new InvalidOperationException("No server address available.");
+        }
+
+        var uri = new UriBuilder(serverAddress + "/chathub");
+
+        // If Kestrel is bound to a wildcard, substitute a real IP
+        if (uri.Host is "0.0.0.0" or "[::]" or "+" or "*")
+        {
+            var addresses = await Dns.GetHostAddressesAsync(
+                System.Environment.MachineName);
+            var ip = addresses.FirstOrDefault(a =>
+                a.AddressFamily == AddressFamily.InterNetwork
+                && !IPAddress.IsLoopback(a));
+
+            if (ip is null)
+            {
+                throw new InvalidOperationException("No suitable IP address.");
+            }
+
+            uri.Host = ip.ToString();
+        }
+
+        hubConnection = new HubConnectionBuilder()
+            .WithUrl(uri.Uri)
+            .Build();
+
+        hubConnection.On<ChatMessage>("ReceiveMessage", (message) =>
+        {
+            ...
+        });
+
+        await hubConnection.StartAsync();
+    }
+}
+```
+
 ## Additional server-side resources
 
 * [Server-side host and deployment guidance: SignalR configuration](xref:blazor/host-and-deploy/server/index#signalr-configuration)

aspnetcore/blazor/project-structure.md

@@ -63,11 +63,15 @@ The `Components` folder of the server project holds the app's server-side Razor
 
 The `Components/Pages` folder of the server project contains the app's routable server-side Razor components. The route for each page is specified using the [`@page`](xref:mvc/views/razor#page) directive.
 
-moniker range=">= aspnetcore-10.0"
+:::moniker-end
+
+:::moniker range=">= aspnetcore-10.0"
 
 The `NotFound` component (`NotFound.razor`) implements a Not Found page to display when content isn't found for a request path. For more information, see <xref:blazor/fundamentals/navigation#not-found-responses>.
 
-moniker-end
+:::moniker-end
+
+:::moniker range=">= aspnetcore-8.0"
 
 The `App` component (`App.razor`) is the root component of the app with HTML `<head>` markup, the `Routes` component, and the Blazor `<script>` tag. The root component is the first component that the app loads.
 
@@ -316,28 +320,28 @@ Project structure:
   * `NavMenu` component (`NavMenu.razor`): Implements sidebar navigation. Includes the [`NavLink` component](xref:blazor/fundamentals/navigation#navlink-component) (<xref:Microsoft.AspNetCore.Components.Routing.NavLink>), which renders navigation links to other Razor components. The <xref:Microsoft.AspNetCore.Components.Routing.NavLink> component automatically indicates a selected state when its component is loaded, which helps the user understand which component is currently displayed.
   * `NavMenu.razor.css`: Stylesheet for the app's navigation menu.
 
-moniker-end
+:::moniker-end
 
-moniker range=">= aspnetcore-10.0"
+:::moniker range=">= aspnetcore-10.0"
 
 * `Pages` folder: Contains the Blazor app's routable Razor components (`.razor`). The route for each page is specified using the [`@page`](xref:mvc/views/razor#page) directive. The template includes the following components:
   * `Counter` component (`Counter.razor`): Implements the Counter page.
   * `Index` component (`Index.razor`): Implements the Home page.
   * `Weather` component (`Weather.razor`): Implements the Weather page.
   * `NotFound` component (`NotFound.razor`): Implements a Not Found page to display when content isn't found for a request path. For more information, see <xref:blazor/fundamentals/navigation#not-found-responses>.
 
-moniker-end
+:::moniker-end
 
-moniker range=">= aspnetcore-8.0 < aspnetcore-10.0"
+:::moniker range=">= aspnetcore-8.0 < aspnetcore-10.0"
 
 * `Pages` folder: Contains the Blazor app's routable Razor components (`.razor`). The route for each page is specified using the [`@page`](xref:mvc/views/razor#page) directive. The template includes the following components:
   * `Counter` component (`Counter.razor`): Implements the Counter page.
   * `Index` component (`Index.razor`): Implements the Home page.
   * `Weather` component (`Weather.razor`): Implements the Weather page.
 
-moniker-end
+:::moniker-end
 
-moniker range=">= aspnetcore-8.0"
+:::moniker range=">= aspnetcore-8.0"
 
 * `_Imports.razor`: Includes common Razor directives to include in the app's components (`.razor`), such as [`@using`](xref:mvc/views/razor#using) directives for namespaces.
 

aspnetcore/tutorials/web-api-help-pages-using-swagger.md

@@ -1,11 +1,12 @@
 ---
 title: ASP.NET Core web API documentation with Swagger / OpenAPI
+ai-usage: ai-assisted
 author: RicoSuter
 description: This tutorial provides a walkthrough of adding Swagger to generate documentation and help pages for a web API app.
 ms.author: wpickett
 ms.custom: mvc
 monikerRange: ">= aspnetcore-3.1 <= aspnetcore-8.0"
-ms.date: 4/25/2024
+ms.date: 02/23/2026
 uid: tutorials/web-api-help-pages-using-swagger
 ---
 # ASP.NET Core web API documentation with Swagger / OpenAPI
@@ -14,6 +15,15 @@ uid: tutorials/web-api-help-pages-using-swagger
 
 By [Rico Suter](https://blog.rsuter.com/)
 
+This article covers using **Swagger** tooling — provided by the [Swashbuckle.AspNetCore](https://github.com/domaindrivendev/Swashbuckle.AspNetCore) and [NSwag](https://github.com/RicoSuter/NSwag) packages — to generate OpenAPI documentation and interactive help pages for ASP.NET Core web APIs.
+
+In .NET 9 and later, ASP.NET Core includes built-in OpenAPI support that replaces Swashbuckle as the default. Swashbuckle is no longer included in project templates, but it remains available as a community package you can add manually.
+
+* To understand the built‑in OpenAPI features, see <xref:fundamentals/openapi/overview?view=aspnetcore-9.0&preserve-view=true>.
+* To add Swagger UI for interactive exploration or local ad‑hoc testing alongside the built-in OpenAPI support, see <xref:fundamentals/openapi/using-openapi-documents#use-swagger-ui-for-local-ad-hoc-testing>.
+
+The following instructions apply to projects using Swashbuckle or NSwag with ASP.NET Core 8.0 and earlier.
+
 [Swagger](https://swagger.io/) ([OpenAPI](https://www.openapis.org/)) is a language-agnostic specification for describing REST APIs. It allows both computers and humans to understand the capabilities of a REST API without direct access to the source code. Its main goals are to:
 
 * Minimize the amount of work needed to connect decoupled services.
@@ -147,12 +157,14 @@ In the preceding code, the `/weatherforecast` endpoint doesn't need authorizatio
 The following Curl passes a JWT token to test the Swagger UI endpoint:
 
 ```bash
-curl -i -H "Authorization: Bearer {token}" https://localhost:{port}/swagger/v1/swagger.json
+curl -i -H "Authorization: Bearer {TOKEN}" https://localhost:{PORT}/swagger/v1/swagger.json
 ```
 
+where the `{TOKEN}` placeholder is the JWT bearer token and the `{PORT}` placeholder is the port number.
+
 For more information on testing with JWT tokens, see <xref:security/authentication/jwt>.
 
-## Generate an XML documentation file at compile time.
+## Generate an XML documentation file at compile time
 
 See [GenerateDocumentationFile](/dotnet/core/project-sdk/msbuild-props#generatedocumentationfile) for more information.