Lessons from Blazor WASM in Production
In this talk from the dotnet channel, the presenters examine what worked, what needed adjustment, and how their expectations of Blazor WebAssembly changed through production use.
Production experience and migration
The discussion draws on converting a large, complex ASP.NET Web Forms interface with more than 180 components to Blazor WebAssembly. The team’s assessment is positive: Blazor WASM met expectations, but not quite in the way they originally envisaged.
The talk covers four areas:
- Migration strategy: The approach to moving the existing Web Forms UI to Blazor WebAssembly.
- Authentication and architecture: Authentication considerations and the application’s general architectural design.
- Production issues: Problems encountered while using Blazor WASM in a real application.
- Performance pitfalls and solutions: Performance challenges and the practical fixes used to address them.
The central takeaway is that Blazor WebAssembly worked well for this migration, while still requiring adjustments to resolve production issues and performance problems.