State Management in Blazor Apps
summary
Compares Blazor WebAssembly (state in browser memory lost on refresh) and Server Blazor (state kept in server circuits but lost if server restarts), and shows three concrete solutions that work: a service-registered singleton for in-app state (counter demo), browser caching via localStorage JSON serialization with a StorageHelper component and JS interop, and server-side persistence via an API (demo uses an in-memory dictionary). Includes a sharable Razor class library, MVVM property-change hooks, and links to the GitHub repo and Blazor State package.
AI-written summary · about
chapters (15)
- 0:00Introduction to Blazor State
- 1:08State management challenges
- 4:13WebAssembly vs server state
- 5:55Handling server-side state
- 7:56Architecting shared solutions
- 12:07State via service registration
- 13:48Implementing a counter service
- 16:56Browser storage options
- 18:22Using local storage in Blazor
- 22:04Creating a storage helper
- 24:52Optimizing state updates
- 29:49Security considerations
- 30:50Server-side persistence
- 35:16Summary of state approaches
- 37:48Q&A session
related talks
01h 03mState management in Blazor
16mFull stack web in .NET 8 with Blazor
49mArchitecting Blazor applications – An Angular inspired approach
57mRunning Blazor in production, lessons learned
49mArchitecting Blazor applications – An Angular inspired approach
51mHands-on Development Experience Using wasm Blazor
49mBuilding Event Driven User Interfaces
53mArchitecting Blazor Applications: An Angular inspired approach