Blazor WASM State Management topic

[taylorchasewhite]

Are there plans with the 3.2 release to add examples / best practices for proper state management in Blazor Web Assembly?

I know this is all Blazor Server, but given that Blazor WebAssembly is a common pattern too, I figure this is a fair question :)

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ae14b3e3-3271-b919-9e0a-6f317a6b2d2d
• Version Independent ID: e5e1273b-195e-5da1-b4aa-66bbcff1425b
• Content: ASP.NET Core Blazor state management
• Content Source: aspnetcore/blazor/state-management.md
• Product: aspnet-core
• Technology: aspnetcore-blazor
• GitHub Login: @guardrex
• Microsoft Alias: riande

[guardrex]

@taylorchasewhite While we wait for triage and engineering guidance ...

• WRT state management in secured WASM apps (i.e., not losing state across sign in/sign out), I'm working on that now on Update Blazor WASM security state container #18652.
• WRT just general state management, Idk if Microsoft.AspNetCore.ProtectedBrowserStorage works in WASM apps. @mkArtakMSFT may know, or you can certainly try to use it and see what happens. 🤞 Worse-case tho, one would implement their own state container service and have some methods to read and restore state from local/session storage.

@mkArtakMSFT, if we proceed on this one, the options are:

• Change this doc to cover both WASM and Server in separate high-level sections (H2s) with the current Blazor Server content rolling in under the Server section.

• Create a new doc for state management in WASM. Seems like a better choice. However, we would need a node for this approach, perhaps with an Overview topic for the node with some common coverage ...

  • State management (ToC node)
    • Blazor WebAssembly
      • UID: blazor/state-management/webassembly
      • Physical: blazor/state-management/webassembly.md
    • Blazor Server
      • UID: blazor/state-management/server
      • Physical: blazor/state-management/server.md

I'll need to know either way ...

• More about Microsoft.AspNetCore.ProtectedBrowserStorage working in WASM apps ... I can test and find that out on my own tho.
• Which state management strategies should we cover in addition to creating a state management container for their app?
  • Cookies
  • URL
  • IndexedDB
  • Caching
  • Other 3rd party key-value or dB storage options (we could at least have a link list to other client-side 3rd party tech, like the way we do for config providers)

[mkArtakMSFT]

@guardrex, ProtectedBrowserStorage support is now in (dotnet/aspnetcore#23553). @MackinnonBuck can you share a small sample showing how to use the new ProtectedBrowserStorage?

[mkArtakMSFT]

Also, I do like the idea of having a separate node for Blazor WebAssembly state management: Create a new doc for state management in WASM, as you referred to it.

[mkArtakMSFT]

As for the categories (your last question), maybe we should hold on for now. Let's roll the simple state management doc and then see how community will react and tell us what more they will need.