Register persistent service for declarative model (#35359)

Author: guardrex

aspnetcore/blazor/components/prerender.md

@@ -199,7 +199,7 @@ In the following example that serializes state for multiple components of the sa
 }
 ```
 
-In the following example that serializes state for a service:
+In the following example that serializes state for a dependency injection service:
 
 * Properties annotated with the `[SupplyParameterFromPersistentComponentState]` attribute are serialized during prerendering and deserialized when the app becomes interactive.
 * The `AddPersistentService` method is used to register the service for persistence. The render mode is required because the render mode can't be inferred from the service type. Use any of the following values:
@@ -211,6 +211,8 @@ In the following example that serializes state for a service:
 > [!NOTE]
 > Only persisting scoped services is supported.
 
+<!-- UPDATE 10.0 - Flesh out with a fully-working example. -->
+
 `CounterService.cs`:
 
 ```csharp

aspnetcore/blazor/fundamentals/static-files.md

@@ -240,9 +240,15 @@ In the project file (`.csproj`), the `<WriteImportMapToHtml>` property is set to
 
 When resolving imports for JavaScript interop, the import map is used by the browser resolve fingerprinted files.
 
+Any script in `index.html` with the fingerprint marker is fingerprinted by the framework. For example, a script file named `scripts.js` in the app's `wwwroot/js` folder is fingerprinted by adding `#[.{fingerprint}]` before the file extension (`.js`):
+
+```html
+<script src="js/scripts#[.{fingerprint}].js"></script>
+```
+
 ## Fingerprint client-side static assets in Blazor Web Apps
 
-For client-side rendering (CSR) in Blazor Web Apps (Interactive Auto or Interactive WebAssembly render modes), static asset server-side [fingerprinting](https://wikipedia.org/wiki/Fingerprint_(computing)) is enabled by adopting [Map Static Assets routing endpoint conventions (`MapStaticAssets`)](xref:fundamentals/map-static-files), [`ImportMap` component](xref:blazor/fundamentals/static-files#importmap-component), and the <xref:Microsoft.AspNetCore.Components.ComponentBase.Assets?displayProperty=nameWithType> property (`@Assets["..."]`).
+For client-side rendering (CSR) in Blazor Web Apps (Interactive Auto or Interactive WebAssembly render modes), static asset server-side [fingerprinting](https://wikipedia.org/wiki/Fingerprint_(computing)) is enabled by adopting [Map Static Assets routing endpoint conventions (`MapStaticAssets`)](xref:fundamentals/map-static-files), [`ImportMap` component](xref:blazor/fundamentals/static-files#importmap-component), and the <xref:Microsoft.AspNetCore.Components.ComponentBase.Assets?displayProperty=nameWithType> property (`@Assets["..."]`). For more information, see <xref:fundamentals/map-static-files>.
 
 To fingerprint additional JavaScript modules for CSR, use the `<StaticWebAssetFingerprintPattern>` item in the app's project file (`.csproj`). In the following example, a fingerprint is added for all developer-supplied `.mjs` files in the app:
 

aspnetcore/blazor/state-management.md

@@ -57,12 +57,37 @@ An app can only persist *app state*. UIs can't be persisted, such as component i
 
 Common locations exist for persisting state:
 
+:::moniker range=">= aspnetcore-10.0"
+
+* [Declarative model for persistent state](#declarative-model-for-persisting-state-server)
+* [Server-side storage](#server-side-storage-server)
+* [URL](#url-server)
+* [Browser storage](#browser-storage-server)
+* [In-memory state container service](#in-memory-state-container-service)
+* [Cascading values and parameters](#cascading-values-and-parameters)
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-10.0"
+
 * [Server-side storage](#server-side-storage-server)
 * [URL](#url-server)
 * [Browser storage](#browser-storage-server)
 * [In-memory state container service](#in-memory-state-container-service)
 * [Cascading values and parameters](#cascading-values-and-parameters)
 
+:::moniker-end
+
+:::moniker range=">= aspnetcore-10.0"
+
+<h2 id="declarative-model-for-persisting-state-server">Declarative model for persisting state</h2>
+
+<!-- UPDATE 10.0 - API cross-link -->
+
+Establish declarative state in a dependency injection service for use around the app by calling `RegisterPersistentService` on the Razor components builder (<xref:Microsoft.Extensions.DependencyInjection.RazorComponentsServiceCollectionExtensions.AddRazorComponents%2A>) with a custom service type and render mode. For more information, see <xref:blazor/components/prerender#persist-prerendered-state>.
+
+:::moniker-end
+
 <h2 id="server-side-storage-server">Server-side storage</h2>
 
 For permanent data persistence that spans multiple users and devices, the app can use server-side storage. Options include:
@@ -618,12 +643,37 @@ An app can only persist *app state*. UIs can't be persisted, such as component i
 
 Common locations exist for persisting state:
 
+:::moniker range=">= aspnetcore-10.0"
+
+* [Declarative model for persistent state](#declarative-model-for-persisting-state-wasm)
+* [Server-side storage](#server-side-storage-wasm)
+* [URL](#url-wasm)
+* [Browser storage](#browser-storage-wasm)
+* [In-memory state container service](#in-memory-state-container-service)
+* [Cascading values and parameters](#cascading-values-and-parameters)
+
+:::moniker-end
+
+:::moniker range="< aspnetcore-10.0"
+
 * [Server-side storage](#server-side-storage-wasm)
 * [URL](#url-wasm)
 * [Browser storage](#browser-storage-wasm)
 * [In-memory state container service](#in-memory-state-container-service)
 * [Cascading values and parameters](#cascading-values-and-parameters)
 
+:::moniker-end
+
+:::moniker range=">= aspnetcore-10.0"
+
+<h2 id="declarative-model-for-persisting-state-wasm">Declarative model for persisting state</h2>
+
+<!-- UPDATE 10.0 - API cross-link -->
+
+Establish declarative state in a dependency injection service for use around the app by calling `RegisterPersistentService` on the Razor components builder (<xref:Microsoft.Extensions.DependencyInjection.RazorComponentsServiceCollectionExtensions.AddRazorComponents%2A>) with a custom service type and render mode. For more information, see <xref:blazor/components/prerender#persist-prerendered-state>.
+
+:::moniker-end
+
 <h2 id="server-side-storage-wasm">Server-side storage</h2>
 
 For permanent data persistence that spans multiple users and devices, the app can use independent server-side storage accessed via a web API. Options include:

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

@@ -130,7 +130,7 @@ Last year, the release of .NET 9 introduced [server-side fingerprinting](https:/
 
 In standalone Blazor WebAssembly apps during build/publish, the framework overrides placeholders in `index.html` with values computed during build to fingerprint static assets. A fingerprint is placed into the `blazor.webassembly.js` script file name.
 
-The following changes must be made in the `wwwwoot/index.html` file to adopt the fingerprinting feature. The standalone Blazor WebAssembly project template will be updated to include these changes in an upcoming preview release:
+The following markup must be present in the `wwwwoot/index.html` file to adopt the fingerprinting feature:
 
 ```diff
 <head>
@@ -161,6 +161,12 @@ In the project file (`.csproj`), add the `<WriteImportMapToHtml>` property set t
 </Project>
 ```
 
+Any script in `index.html` with the fingerprint marker is fingerprinted by the framework. For example, a script file named `scripts.js` in the app's `wwwroot/js` folder is fingerprinted by adding `#[.{fingerprint}]` before the file extension (`.js`):
+
+```html
+<script src="js/scripts#[.{fingerprint}].js"></script>
+```
+
 To fingerprint additional JS modules in standalone Blazor WebAssembly apps, use the `<StaticWebAssetFingerprintPattern>` property in the app's project file (`.csproj`).
 
 In the following example, a fingerprint is added for all developer-supplied `.mjs` files in the app:
@@ -281,7 +287,7 @@ else
 }
 ```
 
-For more information, see <xref:blazor/components/prerender?view=aspnetcore-10.0#persist-prerendered-state>. Additional API implementation notes, which are subject to change at any time, are available in [[Blazor] Support for declaratively persisting component and services state (`dotnet/aspnetcore` #60634)](https://github.com/dotnet/aspnetcore/pull/60634).
+State can be serialized for multiple components of the same type, and you can establish declarative state in a service for use around the app by calling `RegisterPersistentService` on the Razor components builder (<xref:Microsoft.Extensions.DependencyInjection.RazorComponentsServiceCollectionExtensions.AddRazorComponents%2A>) with a custom service type and render mode. For more information, see <xref:blazor/components/prerender?view=aspnetcore-10.0#persist-prerendered-state>.
 
 <!-- PREVIEW 4