[11.0 P4] Blazor What's New feature coverage

Author: guardrex

aspnetcore/blazor/components/virtualization.md

@@ -274,6 +274,34 @@ The <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601> com
 
 :::moniker-end
 
+:::moniker range=">= aspnetcore-11.0"
+
+## Control viewport scroll position behavior when items are dynamically added 
+
+<!-- UPDATE 11.0 - API cross-links -->
+
+Assign a `VirtualizeAnchorMode` value to the `AnchorMode` parameter to control how the viewport behaves at list edges when items are dynamically added:
+
+* `None`: No edge pinning. The viewport stays at current scroll position regardless of item changes.
+* `Beginning`: Pins the viewport to the beginning of the list. When the user is at a scroll position near the top of the list and new items arrive at the beginning, the viewport stays at the top showing the newest items. For example, this pinning behavior is useful for a news feed user experience.
+* `End`: Pins the viewport to the end of the list. When the user is at a scroll position near the bottom of the list and new items arrive at the end, the viewport auto-scrolls to show them. If the user has scrolled away, auto-scroll disengages until they return to the bottom. For example, this pinning behavior is useful for a chat or logging user experience.
+
+The following example pins the viewport to the beginning of a virtualized flight list:
+
+```razor
+<div style="height:500px;overflow-y:scroll">
+    <Virtualize Items="allFlights" Context="flight" AnchorMode="Beginning">
+        <FlightSummary @key="flight.FlightId" Details="@flight.Summary" />
+    </Virtualize>
+</div>
+```
+
+Modes can be combined. For example, assigning `Beginning | End` pins both edges. Combining `None` with other modes is supported but doesn't change the combined value.
+
+`Virtualize.ItemComparer` gets or sets a comparer used to detect whether items were prepended or appended when using class-typed items with an <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601.ItemsProvider%2A> (for more information, see the [Item provider delegate](#item-provider-delegate) section). The comparer determines if the first loaded item changed between provider calls, which indicates items were inserted at the top. For records, the default comparer's value-equality behavior (`EqualityComparer{T}.Default`) works automatically. For an in-memory <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601.Items%2A> assignment, an `ItemComparer` comparer isn't required because the component can detect prepends automatically.
+
+:::moniker-end
+
 ## State changes
 
 When making changes to items rendered by the <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601> component, call <xref:Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged%2A> to enqueue re-evaluation and rerendering of the component. For more information, see <xref:blazor/components/rendering>.

aspnetcore/blazor/debug.md

@@ -164,7 +164,27 @@ Blazor Server: [`Microsoft.AspNetCore.Components.WebAssembly.Server`](https://ww
 
 :::moniker-end
 
-Standalone Blazor WebAssembly: [`Microsoft.AspNetCore.Components.WebAssembly.DevServer`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.DevServer): Development server for use when building Blazor apps. Calls <xref:Microsoft.AspNetCore.Builder.WebAssemblyNetDebugProxyAppBuilderExtensions.UseWebAssemblyDebugging%2A> internally to add middleware for debugging Blazor WebAssembly apps inside Chromium developer tools.
+<!-- UPDATE 11.0 - Activate when the NuGet package is available.
+
+     https://www.nuget.org/packages?q=Microsoft.AspNetCore.Components.Gateway
+
+:::moniker range=">= aspnetcore-11.0"
+
+Standalone Blazor WebAssembly: [`Microsoft.AspNetCore.Components.Gateway`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.Gateway): A lightweight ASP.NET Core host for serving standalone Blazor WebAssembly apps during development and production.
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-11.0"
+
+-->
+
+Standalone Blazor WebAssembly: [`Microsoft.AspNetCore.Components.WebAssembly.DevServer`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.DevServer): Development server for use when building Blazor WebAssembly apps. Calls <xref:Microsoft.AspNetCore.Builder.WebAssemblyNetDebugProxyAppBuilderExtensions.UseWebAssemblyDebugging%2A> internally to add middleware for debugging Blazor WebAssembly apps inside Chromium developer tools.
+
+<!-- UPDATE 11.0 - Activate when the NuGet package is available.
+
+:::moniker-end
+
+-->
 
 :::moniker range="< aspnetcore-8.0"
 

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

@@ -181,11 +181,34 @@ A standalone Blazor WebAssembly frontend app demonstrates user authentication an
 
 The app uses the following NuGet packages:
 
+<!-- UPDATE 11.0 - Activate when the NuGet package is available.
+
+     https://www.nuget.org/packages?q=Microsoft.AspNetCore.Components.Gateway
+
+:::moniker range=">= aspnetcore-11.0"
+
+* [`Microsoft.AspNetCore.Components.WebAssembly.Authentication`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.Authentication)
+* [`Microsoft.Extensions.Http`](https://www.nuget.org/packages/Microsoft.Extensions.Http)
+* [`Microsoft.AspNetCore.Components.WebAssembly`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly)
+* [`Microsoft.AspNetCore.Components.Gateway`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.Gateway)
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-11.0"
+
+-->
+
 * [`Microsoft.AspNetCore.Components.WebAssembly.Authentication`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.Authentication)
 * [`Microsoft.Extensions.Http`](https://www.nuget.org/packages/Microsoft.Extensions.Http)
 * [`Microsoft.AspNetCore.Components.WebAssembly`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly)
 * [`Microsoft.AspNetCore.Components.WebAssembly.DevServer`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.DevServer)
 
+<!-- UPDATE 11.0 - Activate when the NuGet package is available.
+
+:::moniker-end
+
+-->
+
 ### Sample app code
 
 The `Models` folder contains the app's models:

aspnetcore/blazor/state-management/server.md

@@ -213,7 +213,7 @@ To persist temporary data between HTTP requests during static server-side render
 `TempData`:
 
 * Is available when <xref:Microsoft.Extensions.DependencyInjection.RazorComponentsServiceCollectionExtensions.AddRazorComponents%2A> is called in the app's `Program` file.
-* Is provided as a cascading value with the [`[CascadingParameter]` attribute](xref:blazor/components/cascading-values-and-parameters#cascadingparameter-attribute).
+* Is provided as a cascading value with the [`[CascadingParameter]` attribute](xref:blazor/components/cascading-values-and-parameters#cascadingparameter-attribute) or the `[SupplyParameterFromTempData]` parameter attribute.
 * Is accessed by key (string).
 * Supports primitives, <xref:System.DateTime>, <xref:System.Guid>, enums, and collections (arrays, <xref:System.Collections.Generic.List%601>, <xref:System.Collections.Generic.Dictionary%602>).
 * Stores `object?` values, requiring runtime casting (example: `var message = TempData["Message"] as string`). IntelliSense and type checking aren't supported.
@@ -224,6 +224,16 @@ To persist temporary data between HTTP requests during static server-side render
 public ITempData? TempData { get; set; }
 ```
 
+When supplied to a parameter for simple read/write of a single value, use the `[SupplyParameterFromTempData]` attribute without or with a key (string):
+
+```csharp
+[SupplyParameterFromTempData]
+public string? Message { get; set; }
+
+[SupplyParameterFromTempData(Name = "flash_message")]
+public string? FlashMessage { get; set; }
+```
+
 The `ITempData` interface provides the following methods for controlling value lifecycle:
 
 * `Get`: Gets the value associated with the specified key and schedules the data for deletion.
@@ -286,15 +296,16 @@ Browsers enforce a 4 KB cookie size limit. `TempData` automatically uses <xref:M
 
 In the following example, a form displays a message that's retained in `TempData` after the form is submitted (a new request).
 
-`Pages/TempDataExample.razor`:
+`Pages/TempDataExample1.razor`:
 
 ```razor
-@page "/tempdata-example"
+@page "/tempdata-example-1"
 @inject NavigationManager NavigationManager
 
 <p>@message</p>
 
-<form @onsubmit="HandleSubmit">
+<form method="post" @formname="SetMessage" @onsubmit="Submit">
+    <AntiforgeryToken />
     <button type="submit">Submit</button>
 </form>
 
@@ -310,7 +321,7 @@ In the following example, a form displays a message that's retained in `TempData
         message = TempData?.Get("Message") as string ?? "No message";
     }
 
-    private void HandleSubmit()
+    private void Submit()
     {
         TempData!["Message"] = "Form submitted successfully!";
         NavigationManager.NavigateTo("/tempdata-example", forceLoad: true);
@@ -346,6 +357,33 @@ protected override void OnInitialized()
 }
 ```
 
+Similar to the preceding example but when only simple read/write of a single value is required, the following example uses the `[SupplyParameterFromTempData]` attribute.
+
+`Pages/TempDataExample2.razor`:
+
+```razor
+@page "/tempdata-example-2"
+@inject NavigationManager NavigationManager
+
+<p>@Message</p>
+
+<form method="post" @formname="SetMessage" @onsubmit="Submit">
+    <AntiforgeryToken />
+    <button type="submit">Submit</button>
+</form>
+
+@code {
+    [SupplyParameterFromTempData]
+    public string? Message { get; set; }
+
+    private void Submit()
+    {
+        Message = "Form submitted successfully!";
+        NavigationManager.NavigateTo("/tempdata-example", forceLoad: true);
+    }
+}
+```
+
 ### Permanent data persistence
 
 :::moniker-end

aspnetcore/blazor/tooling.md

@@ -494,9 +494,25 @@ For more information, see the following resources:
 
 ## Blazor project templates and template options
 
+:::moniker range=">= aspnetcore-11.0"
+
+* Blazor Web App project template: `blazor`
+* Standalone Blazor WebAssembly app project template: `blazorwasm`
+* [Service defaults library for Blazor WebAssembly apps](#service-defaults-library-for-blazor-webassembly-apps): `blazor-wasm-servicedefaults`
+
+> [!NOTE]
+> The "Hosted" Blazor WebAssembly project template option isn't available in .NET 8 or later. To create a hosted Blazor WebAssembly app, a **Framework** option earlier than .NET 8 must be selected with the **ASP.NET Core Hosted** checkbox. However, we recommend a Blazor Web App for all new Blazor development in .NET 8 or later. For more information, see the following resources:
+>
+> * <xref:blazor/index#build-a-full-stack-web-app-with-blazor>
+> * <xref:aspnetcore-8#new-blazor-web-app-template>
+> * <xref:blazor/project-structure#blazor-web-app>
+> * <xref:migration/70-to-80#convert-a-hosted-blazor-webassembly-app-into-a-blazor-web-app>
+
+:::moniker-end
+
 The Blazor framework provides project templates for creating new apps. The templates are used to create new Blazor projects and solutions regardless of the tooling that you select for Blazor development (Visual Studio, Visual Studio Code, or the [.NET command-line interface (CLI)](/dotnet/core/tools/)):
 
-:::moniker range=">= aspnetcore-8.0"
+:::moniker range=">= aspnetcore-8.0 < aspnetcore-11.0"
 
 * Blazor Web App project template: `blazor`
 * Standalone Blazor WebAssembly app project template: `blazorwasm`
@@ -604,6 +620,32 @@ For more information on template options, see the following resources:
 
 :::moniker-end
 
+:::moniker range=">= aspnetcore-11.0"
+
+## Service defaults library for Blazor WebAssembly apps
+
+The `blazor-wasm-servicedefaults` project template creates a service default library for Blazor WebAssembly apps with .NET Aspire integration.
+
+The template features:
+
+* [OpenTelemetry](https://github.com/open-telemetry/opentelemetry-dotnet) support: Logging, metrics, and tracing with standard OTLP exporter.
+* Service discovery integration via the [`Microsoft.Extensions.ServiceDiscovery` NuGet package](https://www.nuget.org/packages/Microsoft.Extensions.ServiceDiscovery).
+* HTTP resilience using the standard resilience handler via the [`Microsoft.Extensions.Http.Resilience` NuGet package](https://www.nuget.org/packages/Microsoft.Extensions.Http.Resilience).
+
+Example template usage with an output name of `BlazorSample.ServiceDefaults`:
+
+```dotnetcli
+dotnet new blazor-wasm-servicedefaults -o BlazorSample.ServiceDefaults
+```
+
+Reference the library from the Blazor WebAssembly client and make the following call in the app's `Program` file:
+
+```csharp
+builder.AddBlazorClientServiceDefaults();
+```
+
+:::moniker-end
+
 ## Additional resources
 
 :::moniker range=">= aspnetcore-6.0"

aspnetcore/release-notes/aspnetcore-11/includes/blazor.md

@@ -112,14 +112,52 @@ TempData is available when <xref:Microsoft.Extensions.DependencyInjection.RazorC
 public ITempData? TempData { get; set; }
 ```
 
-For more information, see <xref:blazor/state-management/server?view=aspnetcore-11.0#server-side-storage>.
+When supplied to a parameter for simple read/write of a single value, use the `[SupplyParameterFromTempData]` attribute:
+
+```csharp
+[SupplyParameterFromTempData]
+public string? Message { get; set; }
+```
+
+For more information, see <xref:blazor/state-management/server?view=aspnetcore-11.0#temporary-data-persistence>.
 
 ### New Blazor Web Worker template (`blazorwebworker`)
 
 Blazor WebAssembly apps can perform heavy computing on the client, but doing so on the UI thread interferes with UI rendering and negatively affects the user experience. In .NET 10, we added an article with a sample app to make offloading heavy work from the UI thread to a Web Worker easier. For .NET 11, we've added the Blazor Web Worker project template (`blazorwebworker`), which provides infrastructure for running .NET code in a Web Worker in Blazor WebAssembly apps. For more information, see <xref:blazor/blazor-web-workers?view=aspnetcore-11.0>.
 
-### `Virtualize` adapts to variable-height items at runtime
+### Virtualization enhancements
+
+* The <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601> component no longer assumes every item has the same height. The component now adapts to measured item sizes at runtime, which reduces incorrect spacing and scrolling when item heights vary. These updates include an update to the default value of <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601.OverscanCount%2A?displayProperty=nameWithType>, which was `3` in .NET 10 or earlier and now changes to `15` in .NET 11 or later. The change in default value increases the precision of average item height calculations.
+
+  For more information, see the *Item size* and *Overscan count* sections of <xref:blazor/components/virtualization?view=aspnetcore-11.0#item-size>.
+
+* Use the new `AnchorMode` parameter to control how the viewport behaves at list edges when items are dynamically added:
+
+  * `None`: No edge pinning. The viewport stays at current scroll position regardless of item changes.
+  * `Beginning`: Pins the viewport to the beginning of the list. For example, this pinning behavior is useful for a news feed user experience.
+  * `End`: Pins the viewport to the end of the list. For example, this pinning behavior is useful for a chat or logging user experience.
+
+  In the following example, the virtualized content is pinned to the beginning of the list:
+
+  ```razor
+  <Virtualize AnchorMode="Beginning" ...>
+      ...
+  </Virtualize>
+  ```
+
+  For more information, see <xref:blazor/components/virtualization?view=aspnetcore-11.0#control-viewport-scroll-position-behavior-when-items-are-dynamically-added>.
+
+### New service defaults library project template for Blazor WebAssembly apps
+
+The `blazor-wasm-servicedefaults` project template creates a service default library for Blazor WebAssembly apps with .NET Aspire integration. For more information, see <xref:blazor/tooling?view=aspnetcore-11.0#service-defaults-library-for-blazor-webassembly-apps>.
+
+### New development server for Blazor WebAssembly apps
+
+<!-- UPDATE 11.0 - Link to package when it's out.
+
+     [`Microsoft.AspNetCore.Components.Gateway`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.Gateway)
+-->
 
-The <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601> component no longer assumes every item has the same height. The component now adapts to measured item sizes at runtime, which reduces incorrect spacing and scrolling when item heights vary. These updates include an update to the default value of <xref:Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize%601.OverscanCount%2A?displayProperty=nameWithType>, which was `3` in .NET 10 or earlier and now changes to `15` in .NET 11 or later. The change in default value increases the precision of average item height calculations.
+`Microsoft.AspNetCore.Components.Gateway` is a lightweight ASP.NET Core host that replaces [`Microsoft.AspNetCore.Components.WebAssembly.DevServer`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.WebAssembly.DevServer) for serving standalone Blazor WebAssembly applications during development and production.
 
-For more information, see the *Item size* and *Overscan count* sections of <xref:blazor/components/virtualization?view=aspnetcore-11.0#item-size>.
+For more information, see [[Blazor] Replace DevServer with BlazorGateway for standalone WASM apps (`dotnet/aspnetcore` #65982)](https://github.com/dotnet/aspnetcore/pull/65982).