Merge branch 'dotnet:main' into main

Author: timdeschryver

.github/workflows/issue-processing.yml

@@ -77,7 +77,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: `### 😎 **March!** ***The gateway to spring!*** 🌞
+              body: `### 😎 **Welcome April!** ***Summertime is almost here!*** 🌞
 
             A green dinosaur 🦖 will be along shortly to assist. *Stand-by ........*`
             })

.openpublishing.redirection.json

@@ -1277,6 +1277,11 @@
             "source_path": "aspnetcore/blazor/security/server/blazor-web-app-with-oidc.md",
             "redirect_url": "/aspnet/core/blazor/security/blazor-web-app-with-oidc",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/http-caching-issues.md",
+            "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly-caching/http-caching-issues",
+            "redirect_document_id": false
         }
     ]
 }

aspnetcore/blazor/call-web-api.md

@@ -680,7 +680,7 @@ public class CookieHandler : DelegatingHandler
 The `CookieHandler` is registered in the `Program` file:
 
 ```csharp
-builder.Services.AddScoped<CookieHandler>();
+builder.Services.AddTransient<CookieHandler>();
 ```
 
 The message handler is added to any preconfigured <xref:System.Net.Http.HttpClient> that requires cookie authentication:

aspnetcore/blazor/components/dynamiccomponent.md

@@ -143,8 +143,9 @@ In the following example, a Razor component renders a component based on the use
 
 In the preceding example:
 
-* Component names are used as the option values using the [`nameof` operator](/dotnet/csharp/language-reference/operators/nameof), which returns component names as constant strings.
-* The namespace of the app is `BlazorSample`. ***Change the namespace to match your app's namespace.***
+* An <xref:System.Collections.Generic.Dictionary%602> is used to manage components to be displayed.
+* Names serve as the dictionary keys and are provided as selection options.
+* Component types are stored as dictionary values using the [`typeof` operator](/dotnet/csharp/language-reference/operators/type-testing-and-cast#typeof-operator).
 
 ## Pass parameters
 
@@ -197,7 +198,7 @@ The following `RocketLabWithWindowSeat` component (`RocketLabWithWindowSeat.razo
 In the following example:
 
 * Only the `RocketLabWithWindowSeat` component's parameter for a window seat (`WindowSeat`) receives the value of the **`Window Seat`** checkbox.
-* The namespace of the app is `BlazorSample`. ***Change the namespace to match your app's namespace.***
+* Component names are used as dictionary keys using the [`nameof` operator](/dotnet/csharp/language-reference/operators/nameof), which returns component names as constant strings.
 * The dynamically-rendered components are shared components:
   * Shown in this article section: `RocketLabWithWindowSeat` (`RocketLabWithWindowSeat.razor`)
   * Components shown in the [Example](#example) section earlier in this article:
@@ -340,10 +341,7 @@ In the following parent component example, the `ShowDTMessage` method assigns a
 The parent component passes the callback method, `ShowDTMessage` in the parameter dictionary:
 
 * The `string` key is the callback method's name, `OnClickCallback`.
-* The `object` value is created by <xref:Microsoft.AspNetCore.Components.EventCallbackFactory.Create%2A?displayProperty=nameWithType> for the parent callback method, `ShowDTMessage`. Note that the [`this` keyword](/dotnet/csharp/language-reference/keywords/this) isn't supported in C# fields, so a C# property is used for the parameter dictionary.
-
-> [!IMPORTANT]
-> For the following component, modify the code in the `OnDropdownChange` method. Change the namespace name of "`BlazorSample`" in the `Type.GetType()` argument to match your app's namespace.
+* The `object` value is created by <xref:Microsoft.AspNetCore.Components.EventCallbackFactory.Create%2A?displayProperty=nameWithType> for the parent callback method, `ShowDTMessage`. Note that the [`this` keyword](/dotnet/csharp/language-reference/keywords/this) isn't supported in C# field initialization, so a C# property is used for the parameter dictionary.
 
 :::moniker range=">= aspnetcore-8.0"
 

aspnetcore/blazor/components/rendering.md

@@ -33,7 +33,7 @@ Components inherited from <xref:Microsoft.AspNetCore.Components.ComponentBase> s
 
   [!INCLUDE[](~/includes/aspnetcore-repo-ref-source-links.md)]
 
-* The component's [`ShouldRender` method](#suppress-ui-refreshing-shouldrender) returns `false`.
+* The override of the component's [`ShouldRender` method](#suppress-ui-refreshing-shouldrender) returns `false` (the default `ComponentBase` implementation always returns `true`).
 
 ## Control the rendering flow
 
@@ -256,9 +256,9 @@ One way to deal with this scenario is to provide a *state management* class, oft
 
 For approaches to manage state, see the following resources:
 
-* [Server-side in-memory state container service](xref:blazor/state-management?pivots=server#in-memory-state-container-service-server) ([client-side equivalent](xref:blazor/state-management?pivots=webassembly#in-memory-state-container-service-wasm)) section of the *State management* article.
-* [Pass data across a component hierarchy](xref:blazor/components/cascading-values-and-parameters#pass-data-across-a-component-hierarchy) using cascading values and parameters.
 * [Bind across more than two components](xref:blazor/components/data-binding#bind-across-more-than-two-components) using data bindings.
+* [Pass data across a component hierarchy](xref:blazor/components/cascading-values-and-parameters#pass-data-across-a-component-hierarchy) using cascading values and parameters.
+* [Server-side in-memory state container service](xref:blazor/state-management?pivots=server#in-memory-state-container-service-server) ([client-side equivalent](xref:blazor/state-management?pivots=webassembly#in-memory-state-container-service-wasm)) section of the *State management* article.
 
 For the state manager approach, C# events are outside the Blazor rendering pipeline. Call <xref:Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged%2A> on other components you wish to rerender in response to the state manager's events.
 

aspnetcore/blazor/components/virtualization.md

@@ -46,6 +46,8 @@ If the collection contains thousands of flights, rendering the flights takes a l
 Instead of rendering the entire list of flights at once, replace the [`foreach`](/dotnet/csharp/language-reference/keywords/foreach-in) loop in the preceding example with the <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601> component:
 
 * Specify `allFlights` as a fixed item source to <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601.Items%2A?displayProperty=nameWithType>. Only the currently visible flights are rendered by the <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601> component.
+
+  If a non-generic collection supplies the items, for example a collection of <xref:System.Data.DataRow>, follow the guidance in the [Item provider delegate](#item-provider-delegate) section to supply the items.
 * Specify a context for each flight with the `Context` parameter. In the following example, `flight` is used as the context, which provides access to each flight's members.
 
 ```razor
@@ -70,8 +72,7 @@ The <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601> com
 
 * Calculates the number of items to render based on the height of the container and the size of the rendered items.
 * Recalculates and rerenders the items as the user scrolls.
-* Only fetches the slice of records from an external API that correspond to the current visible region, instead of downloading all of the data from the collection.
-* Receives a generic <xref:System.Collections.Generic.ICollection%601> for <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601.Items?displayProperty=nameWithType>. If a non-generic collection supplies the items (for example, a collection of <xref:System.Data.DataRow>), follow the guidance in the [Item provider delegate](#item-provider-delegate) section to supply the items.
+* Only fetches the slice of records from an external API that correspond to the currently visible region, including overscan, when `ItemsProvider` is used instead of `Items` (see the [Item provider delegate](#item-provider-delegate) section).
 
 The item content for the <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601> component can include:
 

aspnetcore/blazor/fundamentals/environments.md

@@ -186,7 +186,7 @@ Obtain the app's environment in a component by injecting <xref:Microsoft.AspNetC
 
 <h1>Environment example</h1>
 
-<p>Environment: @HostEnvironment.Environment</p>
+<p>Environment: @Env.Environment</p>
 ```
 
 :::moniker range=">= aspnetcore-8.0"

aspnetcore/blazor/fundamentals/routing.md

@@ -1609,6 +1609,71 @@ The following HTML markup is rendered:
 > }
 > ```
 
+<xref:Microsoft.AspNetCore.Components.Routing.NavLink> component entries can be dynamically created from the app's components via reflection. The following example demonstrates the general approach for further customization.
+
+For the following demonstration, a consistent, standard naming convention is used for the app's components:
+
+* Routable component file names use Pascal case&dagger;, for example `Pages/ProductDetail.razor`.
+* Routable component file paths match their URLs in kebab case&Dagger; with hyphens appearing between words in a component's route template. For example, a `ProductDetail` component with a route template of `/product-detail` (`@page "/product-detail"`) is requested in a browser at the relative URL `/product-detail`.
+
+&dagger;Pascal case (upper camel case) is a naming convention without spaces and punctuation and with the first letter of each word capitalized, including the first word.  
+&Dagger;Kebab case is a naming convention without spaces and punctuation that uses lowercase letters and dashes between words.
+
+In the Razor markup of the `NavMenu` component (`NavMenu.razor`) under the default `Home` page, <xref:Microsoft.AspNetCore.Components.Routing.NavLink> components are added from a collection:
+
+```diff
+<div class="nav-scrollable" 
+    onclick="document.querySelector('.navbar-toggler').click()">
+    <nav class="flex-column">
+        <div class="nav-item px-3">
+            <NavLink class="nav-link" href="" Match="NavLinkMatch.All">
+                <span class="bi bi-house-door-fill-nav-menu" 
+                    aria-hidden="true"></span> Home
+            </NavLink>
+        </div>
+
++       @foreach (var name in GetRoutableComponents())
++       {
++           <div class="nav-item px-3">
++               <NavLink class="nav-link" 
++                       href="@Regex.Replace(name, @"(\B[A-Z]|\d+)", "-$1").ToLower()">
++                   @Regex.Replace(name, @"(\B[A-Z]|\d+)", " $1")
++               </NavLink>
++           </div>
++       }
+
+    </nav>
+</div>
+```
+
+The `GetRoutableComponents` method in the `@code` block:
+
+```csharp
+public IEnumerable<string> GetRoutableComponents()
+{
+    return Assembly.GetExecutingAssembly()
+        .ExportedTypes
+        .Where(t => t.IsSubclassOf(typeof(ComponentBase)))
+        .Where(c => c.GetCustomAttributes(inherit: true)
+                     .OfType<RouteAttribute>()
+                     .Any())
+        .Where(c => c.Name != "Home" && c.Name != "Error")
+        .OrderBy(o => o.Name)
+        .Select(c => c.Name);
+}
+```
+
+The preceding example doesn't include the following pages in the rendered list of components:
+
+* `Home` page: The page is listed separately from the automatically generated links because it should appear at the top of the list and set the `Match` parameter.
+* `Error` page: The error page is only navigated to by the framework and shouldn't be listed.
+
+:::moniker range=">= aspnetcore-8.0"
+
+For an example of the preceding code in a sample app that you can run locally, obtain the [**Blazor Web App** or **Blazor WebAssembly** sample app](xref:blazor/fundamentals/index#sample-apps).
+
+:::moniker-end
+
 ## ASP.NET Core endpoint routing integration
 
 :::moniker range=">= aspnetcore-8.0"