Merge pull request #34915 from dotnet/main

Author: guardrex

.github/policies/issueManagement-notTriaged.yml

@@ -15,6 +15,9 @@ configuration:
           * 'needs-more-info' label removed
         if:
           - payloadType: Issues
+          - not:
+              isAssignedToUser:
+                user: guardrex
           - or:
           
             - or:

aspnetcore/blazor/components/render-components-outside-of-aspnetcore.md

@@ -16,17 +16,22 @@ uid: blazor/components/render-outside-of-aspnetcore
 
 In the following example, a Razor component is rendered to an HTML string from a console app:
 
-In a command shell, create a new console app project:
+In a command shell, create a new console app project and change the directory to the `ConsoleApp1` folder:
 
 ```dotnetcli
 dotnet new console -o ConsoleApp1
 cd ConsoleApp1
 ```
 
-In a command shell in the `ConsoleApp1` folder, add package references for <xref:Microsoft.AspNetCore.Components.Web?displayProperty=fullName> and <xref:Microsoft.Extensions.Logging?displayProperty=fullName> to the console app:
+Add a package reference for <xref:Microsoft.AspNetCore.Components.Web?displayProperty=fullName>:
 
 ```dotnetcli
 dotnet add package Microsoft.AspNetCore.Components.Web
+```
+
+Add a package reference for <xref:Microsoft.Extensions.Logging?displayProperty=fullName>:
+
+```dotnetcli
 dotnet add package Microsoft.Extensions.Logging
 ```
 
@@ -48,17 +53,15 @@ Add the following `RenderMessage` component to the project.
 
 @code {
     [Parameter]
-    public string Message { get; set; }
+    public string? Message { get; set; }
 }
 ```
 
-Update the `Program` file:
+Replace the code in the `Program` file with the following code:
 
 * Set up dependency injection (<xref:Microsoft.Extensions.DependencyInjection.IServiceCollection>/<xref:Microsoft.Extensions.DependencyInjection.ServiceCollectionContainerBuilderExtensions.BuildServiceProvider%2A>) and logging (<xref:Microsoft.Extensions.DependencyInjection.LoggingServiceCollectionExtensions.AddLogging%2A>/<xref:Microsoft.Extensions.Logging.ILoggerFactory>).
 * Create an <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer> and render the `RenderMessage` component by calling <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A>.
 
-Any calls to <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A> must be made in the context of calling `InvokeAsync` on a component dispatcher. A component dispatcher is available from the <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.Dispatcher?displayProperty=nameWithType> property.
-
 ```csharp
 using Microsoft.AspNetCore.Components;
 using Microsoft.AspNetCore.Components.Web;
@@ -93,6 +96,8 @@ Console.WriteLine(html);
 > [!NOTE]
 > Pass <xref:Microsoft.AspNetCore.Components.ParameterView.Empty?displayProperty=nameWithType> to <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A> when rendering the component without passing parameters.
 
+Any calls to <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A> must be made in the context of calling `InvokeAsync` on a component dispatcher. A component dispatcher is available from the <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.Dispatcher?displayProperty=nameWithType> property.
+
 Alternatively, you can write the HTML to a <xref:System.IO.TextWriter> by calling `output.WriteHtmlTo(textWriter)`.
 
 The task returned by <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A> completes when the component is fully rendered, including completing any asynchronous lifecycle methods. If you want to observe the rendered HTML earlier, call <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.BeginRenderingComponent%2A> instead. Then, wait for the component rendering to complete by awaiting <xref:Microsoft.AspNetCore.Components.Web.HtmlRendering.HtmlRootComponent.QuiescenceTask%2A?displayProperty=nameWithType> on the returned <xref:Microsoft.AspNetCore.Components.Web.HtmlRendering.HtmlRootComponent> instance.

aspnetcore/blazor/fundamentals/signalr.md

@@ -519,7 +519,78 @@ If reconnection fails, the user is instructed to retry or reload the page:
 
 If reconnection succeeds, user state is often lost. Custom code can be added to any component to save and reload user state across connection failures. For more information, see <xref:blazor/state-management>.
 
-:::moniker range=">= aspnetcore-8.0"
+:::moniker range=">= aspnetcore-10.0"
+
+To create UI elements that track reconnection state, the following table describes:
+
+* A set of `components-reconnect-*` CSS classes (**Css class** column) that are set or unset by Blazor on an element with an `id` of `components-reconnect-modal`.
+* A `components-reconnect-state-changed` event (**Event** column) that indicates a reconnection status change.
+
+| CSS class | Event | Indicates&hellip; |
+| --- | --- | --- |
+| `components-reconnect-show` | `show` | A lost connection. The client is attempting to reconnect. The reconnection modal is shown. |
+| `components-reconnect-hide` | `hide` | An active connection is re-established to the server. The reconnection model is closed. |
+| `components-reconnect-retrying` | `retrying` | The client is attempting to reconnect. |
+| `components-reconnect-failed` | `failed` | Reconnection failed, probably due to a network failure. |
+| `components-reconnect-rejected` | `rejected` | Reconnection rejected. |
+
+When the reconnection state change in `components-reconnect-state-changed` is `failed`, call `Blazor.reconnect()` in JavaScript to attempt reconnection.
+
+When the reconnection state change is `rejected`, the server was reached but refused the connection, and the user's state on the server is lost. To reload the app, call `location.reload()` in JavaScript. This connection state may result when:
+
+* A crash in the server-side circuit occurs.
+* The client is disconnected long enough for the server to drop the user's state. Instances of the user's components are disposed.
+* The server is restarted, or the app's worker process is recycled.
+
+The developer adds an event listener on the reconnect modal element to monitor and react to reconnection state changes, as seen in the following example:
+
+```javascript
+const reconnectModal = document.getElementById("components-reconnect-modal");
+reconnectModal.addEventListener("components-reconnect-state-changed", 
+  handleReconnectStateChanged);
+
+function handleReconnectStateChanged(event) {
+  if (event.detail.state === "show") {
+    reconnectModal.showModal();
+  } else if (event.detail.state === "hide") {
+    reconnectModal.close();
+  } else if (event.detail.state === "failed") {
+    Blazor.reconnect();
+  } else if (event.detail.state === "rejected") {
+    location.reload();
+  }
+}
+```
+
+An element with an `id` of `components-reconnect-max-retries` displays the maximum number of reconnect retries:
+
+```html
+<span id="components-reconnect-max-retries"></span>
+```
+
+An element with an `id` of `components-reconnect-current-attempt` displays the current reconnect attempt:
+
+```html
+<span id="components-reconnect-current-attempt"></span>
+```
+
+An element with an `id` of `components-seconds-to-next-attempt` displays the number of seconds to the next reconnection attempt:
+
+```html
+<span id="components-seconds-to-next-attempt"></span>
+```
+
+The Blazor Web App project template includes a `ReconnectModal` component (`Components/Layout/ReconnectModal.razor`) with collocated stylesheet and JavaScript files (`ReconnectModal.razor.css`, `ReconnectModal.razor.js`) that can be customized as needed. These files can be examined in the ASP.NET Core reference source or by inspecting an app created from the Blazor Web App project template. The component is added to the project when the project is created in Visual Studio with **Interactive render mode** set to **Server** or **Auto** or created with the .NET CLI with the option `--interactivity server` (default) or `--interactivity auto`.
+
+* [`ReconnectModal` component](https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/BlazorWeb-CSharp/BlazorWeb-CSharp/Components/Layout/ReconnectModal.razor)
+* [Stylesheet file](https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/BlazorWeb-CSharp/BlazorWeb-CSharp/Components/Layout/ReconnectModal.razor.css)
+* [JavaScript file](https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/BlazorWeb-CSharp/BlazorWeb-CSharp/Components/Layout/ReconnectModal.razor.js)
+
+[!INCLUDE[](~/includes/aspnetcore-repo-ref-source-links.md)]
+
+:::moniker-end
+
+:::moniker range=">= aspnetcore-8.0 < aspnetcore-10.0"
 
 To customize the UI, define a single element with an `id` of `components-reconnect-modal` in the `<body>` element content. The following example places the element in the `App` component.
 
@@ -551,6 +622,8 @@ To customize the UI, define a single element with an `id` of `components-reconne
 
 :::moniker-end
 
+:::moniker range="< aspnetcore-10.0"
+
 ```cshtml
 <div id="components-reconnect-modal">
     Connection lost.<br>Attempting to reconnect...
@@ -562,7 +635,9 @@ To customize the UI, define a single element with an `id` of `components-reconne
 
 Add the following CSS styles to the site's stylesheet.
 
-:::moniker range=">= aspnetcore-8.0"
+:::moniker-end
+
+:::moniker range=">= aspnetcore-8.0 < aspnetcore-10.0"
 
 `wwwroot/app.css`:
 
@@ -574,6 +649,8 @@ Add the following CSS styles to the site's stylesheet.
 
 :::moniker-end
 
+:::moniker range="< aspnetcore-10.0"
+
 ```css
 #components-reconnect-modal {
     display: none;
@@ -604,13 +681,15 @@ The following table describes the CSS classes applied to the `components-reconne
 | `components-reconnect-failed`   | Reconnection failed, probably due to a network failure. To attempt reconnection, call `window.Blazor.reconnect()` in JavaScript. |
 | `components-reconnect-rejected` | Reconnection rejected. The server was reached but refused the connection, and the user's state on the server is lost. To reload the app, call `location.reload()` in JavaScript. This connection state may result when:<ul><li>A crash in the server-side circuit occurs.</li><li>The client is disconnected long enough for the server to drop the user's state. Instances of the user's components are disposed.</li><li>The server is restarted, or the app's worker process is recycled.</li></ul> |
 
-:::moniker range=">= aspnetcore-5.0"
+:::moniker-end
+
+:::moniker range=">= aspnetcore-5.0 < aspnetcore-10.0"
 
 Customize the delay before the reconnection UI appears by setting the `transition-delay` property in the site's CSS for the modal element. The following example sets the transition delay from 500 ms (default) to 1,000 ms (1 second).
 
 :::moniker-end
 
-:::moniker range=">= aspnetcore-8.0"
+:::moniker range=">= aspnetcore-8.0 < aspnetcore-10.0"
 
 `wwwroot/app.css`:
 
@@ -622,7 +701,7 @@ Customize the delay before the reconnection UI appears by setting the `transitio
 
 :::moniker-end
 
-:::moniker range=">= aspnetcore-5.0"
+:::moniker range=">= aspnetcore-5.0 < aspnetcore-10.0"
 
 ```css
 #components-reconnect-modal {

aspnetcore/blazor/security/includes/troubleshoot-server.md

@@ -91,7 +91,7 @@ A functioning app may fail immediately after upgrading either the .NET Core SDK
 1. Delete all of the files in the deployment folder on the server prior to redeploying the app.
 
 > [!NOTE]
-> Use of package versions incompatible with the app's target framework isn't supported. For information on a package, use the [NuGet Gallery](https://www.nuget.org) or [FuGet Package Explorer](https://www.fuget.org).
+> Use of package versions incompatible with the app's target framework isn't supported. For information on a package, use the [NuGet Gallery](https://www.nuget.org).
 
 ### Run the server app
 

aspnetcore/blazor/security/includes/troubleshoot-wasm.md

@@ -91,7 +91,7 @@ A functioning app may fail immediately after upgrading either the .NET Core SDK
 1. Delete all of the files in the deployment folder on the server prior to redeploying the app.
 
 > [!NOTE]
-> Use of package versions incompatible with the app's target framework isn't supported. For information on a package, use the [NuGet Gallery](https://www.nuget.org) or [FuGet Package Explorer](https://www.fuget.org).
+> Use of package versions incompatible with the app's target framework isn't supported. For information on a package, use the [NuGet Gallery](https://www.nuget.org).
 
 :::moniker range="< aspnetcore-8.0"
 

aspnetcore/blazor/security/webassembly/standalone-with-identity/index.md

@@ -361,7 +361,7 @@ A functioning app may fail immediately after upgrading either the .NET Core SDK
 1. Delete all of the files in the deployment folder on the server prior to redeploying the app.
 
 > [!NOTE]
-> Use of package versions incompatible with the app's target framework isn't supported. For information on a package, use the [NuGet Gallery](https://www.nuget.org) or [FuGet Package Explorer](https://www.fuget.org).
+> Use of package versions incompatible with the app's target framework isn't supported. For information on a package, use the [NuGet Gallery](https://www.nuget.org).
 
 ### Inspect the user's claims
 

aspnetcore/fundamentals/openapi/aspnetcore-openapi.md

@@ -259,10 +259,14 @@ Create a new ASP.NET Core Web API (Native AOT) project.
 dotnet new webapiaot
 ```
 
+:::moniker-end
+
+:::moniker range="= aspnetcore-9.0"
+
 Add the Microsoft.AspNetCore.OpenAPI package.
 
 ```console
-dotnet add package Microsoft.AspNetCore.OpenApi --prerelease
+dotnet add package Microsoft.AspNetCore.OpenApi
 ```
 
 Update `Program.cs` to enable generating OpenAPI documents.
@@ -275,12 +279,12 @@ var app = builder.Build();
 + app.MapOpenApi();
 ```
 
+:::moniker-end
+
 Publish the app.
 
 ```console
 dotnet publish
 ```
 
-:::moniker-end
-
 [!INCLUDE[](~/fundamentals/openapi/includes/aspnetcore-openapi6-8.md)]

aspnetcore/host-and-deploy/iis/advanced.md

@@ -5,7 +5,7 @@ description: Advanced configuration with the ASP.NET Core Module and Internet In
 monikerRange: '>= aspnetcore-5.0'
 ms.author: riande
 ms.custom: mvc
-ms.date: 10/09/2023
+ms.date: 03/07/2025
 uid: host-and-deploy/iis/advanced
 ---
 # Advanced configuration of the ASP.NET Core Module and IIS
@@ -18,7 +18,8 @@ This article covers advanced configuration options and scenarios for the ASP.NET
 
 *Only applies when using the in-process hosting model.*
 
-Configure the managed stack size using the `stackSize` setting in bytes in the `web.config` file. The default size is 1,048,576 bytes (1 MB). The following example changes the stack size to 2 MB (2,097,152 bytes):
+:::moniker range="> aspnetcore-9.0"
+Configure the managed stack size using the `stackSize` setting in bytes in hexadecimal in the `web.config` file. The default size is 1,048,576 bytes (1 MB) expressed in hexadecimal. The following example changes the stack size to 2 MB (2,097,152 bytes) in hexadecimal 0x200000:
 
 ```xml
 <aspNetCore processPath="dotnet"
@@ -27,11 +28,31 @@ Configure the managed stack size using the `stackSize` setting in bytes in the `
     stdoutLogFile="\\?\%home%\LogFiles\stdout"
     hostingModel="inprocess">
   <handlerSettings>
-    <handlerSetting name="stackSize" value="2097152" />
+    <handlerSetting name="stackSize" value="200000" />
   </handlerSettings>
 </aspNetCore>
 ```
 
+:::moniker-end
+
+:::moniker range="<= aspnetcore-9.0"
+
+Configure the managed stack size using the `stackSize` setting in bytes in the `web.config` file. The default size is 17,825,792 bytes (17 MB). The following example changes the stack size to 100,000 hex, (1 MB):
+
+```xml
+<aspNetCore processPath="dotnet"
+    arguments=".\MyApp.dll"
+    stdoutLogEnabled="false"
+    stdoutLogFile="\\?\%home%\LogFiles\stdout"
+    hostingModel="inprocess">
+  <handlerSettings>
+    <handlerSetting name="stackSize" value="100000" />
+  </handlerSettings>
+</aspNetCore>
+```
+
+:::moniker-end
+
 ## Disallow rotation on config
 
 The `disallowRotationOnConfigChange` setting is intended for blue/green scenarios where a change to global config should not cause all sites to recycle. When this flag is true, only changes relevant to the site itself will cause it to recycle. For example, a site recycles if its *web.config* changes or something changes that is relevant to the site's path from IIS's perspective. But a general change to *applicationHost.config* would not cause an app to recycle. The following example sets this setting to true:

aspnetcore/introduction-to-aspnet-core.md

@@ -19,7 +19,7 @@ ASP.NET Core is a cross-platform, high-performance, [open-source](https://github
 
 With ASP.NET Core, you can:
 
-* Build web apps and services, [Internet of Things (IoT)](https://www.microsoft.com/internet-of-things/) apps, and mobile backends.
+* Build web apps and services, [Azure IoT (Internet of Things)](https://azure.microsoft.com/solutions/iot) apps, and mobile backends.
 * Use your favorite development tools on Windows, macOS, and Linux.
 * Deploy to the cloud or on-premises.
 * Run on [.NET](/dotnet/core/introduction).
@@ -98,7 +98,7 @@ For a reference guide to migrating ASP.NET 4.x apps to ASP.NET Core, see <xref:m
 
 ASP.NET Core is a cross-platform, high-performance, [open-source](https://github.com/dotnet/aspnetcore) framework for building modern, cloud-enabled, Internet-connected apps. With ASP.NET Core, you can:
 
-* Build web apps and services, [Internet of Things (IoT)](https://www.microsoft.com/internet-of-things/) apps, and mobile backends.
+* Build web apps and services, [Azure IoT (Internet of Things)](https://azure.microsoft.com/solutions/iot) apps, and mobile backends.
 * Use your favorite development tools on Windows, macOS, and Linux.
 * Deploy to the cloud or on-premises.
 * Run on [.NET Core or .NET Framework](/dotnet/articles/standard/choosing-core-framework-server).

aspnetcore/performance/rate-limit.md

@@ -1,11 +1,11 @@
 ---
 title: Rate limiting middleware in ASP.NET Core
-author: tdykstra
+author: rick-anderson
+ms.author: riande
 monikerRange: '>= aspnetcore-7.0'
 description: Learn how limit requests in ASP.NET Core apps
-ms.author: tdykstra
 ms.custom: mvc
-ms.date: 10/29/2022
+ms.date: 03/05/2025
 uid: performance/rate-limit
 ---
 
@@ -44,7 +44,7 @@ The preceding code:
 * Calls `AddFixedWindowLimiter` to create a fixed window limiter with a policy name of `"fixed"` and sets:
 * <xref:System.Threading.RateLimiting.FixedWindowRateLimiterOptions.PermitLimit> to 4 and the time <xref:System.Threading.RateLimiting.FixedWindowRateLimiterOptions.Window> to 12. A maximum of 4 requests per each 12-second window are allowed.
 * <xref:System.Threading.RateLimiting.FixedWindowRateLimiterOptions.QueueProcessingOrder> to <xref:System.Threading.RateLimiting.QueueProcessingOrder.OldestFirst>.
-* <xref:System.Threading.RateLimiting.FixedWindowRateLimiterOptions.QueueLimit> to 2.
+* <xref:System.Threading.RateLimiting.FixedWindowRateLimiterOptions.QueueLimit> to 2 (set this to 0 to disable the queueing mechanism).
 * Calls [UseRateLimiter](/dotnet/api/microsoft.aspnetcore.builder.ratelimiterapplicationbuilderextensions.useratelimiter) to enable rate limiting.
 
 Apps should use [Configuration](xref:fundamentals/configuration/index) to set limiter options. The following code updates the preceding code using [`MyRateLimitOptions`](https://github.com/dotnet/AspNetCore.Docs.Samples/blob/main/fundamentals/middleware/rate-limit/WebRateLimitAuth/Models/MyRateLimitOptions.cs) for configuration:
@@ -140,7 +140,7 @@ The <xref:System.Threading.RateLimiting.PartitionedRateLimiter.CreateChained%2A>
 
 The following code uses `CreateChained`:
 
-:::code language="csharp" source="~/../AspNetCore.Docs.Samples/fundamentals/middleware/rate-limit/WebRate2/Program.cs" id="snippet_3" highlight="21,51":::
+:::code language="csharp" source="~/../AspNetCore.Docs.Samples/fundamentals/middleware/rate-limit/WebRate2/Program.cs" id="snippet_3" highlight="19,20,33":::
 
 For more information, see the [CreateChained source code](https://github.com/dotnet/runtime/blob/79874806d246670ee5fe76e73ce566578fe675c0/src/libraries/System.Threading.RateLimiting/src/System/Threading/RateLimiting/PartitionedRateLimiter.cs#L52-L64)