Architecting Blazor Applications: An Angular inspired approach
summary
Claims that server-side Blazor in .NET Core 3.0 is production-ready while the client WebAssembly model targets .NET 5, and shows a working GitHub dashboard that uses OAuth to fetch repos, branches and issues via the GitHub API over SignalR-rendered HTML diffs. Covers concrete patterns: feature-based folder structure, component forms (inline, code-behind, class-only) and the container/presentation pattern, explains Parameters and EventCallback for communication, notes CSS scoping is not per-component yet and WebAssembly debugging is limited.
AI-written summary · about
chapters (15)
- 0:00Start
- 7:00Full-stack web development in C#
- 7:50Hosting models
- 13:27Options for organizing code
- 16:31What's the correct way?
- 18:43The "Core" folder
- 20:12The "Shared" folder
- 23:57Inline component type
- 25:46Code behind component types
- 28:05Class only components
- 29:42Use code behind components
- 35:14Parameters
- 36:22EventCallbacks
- 37:28Container presentation pattern
- 43:47State container
related talks
49mArchitecting Blazor applications – An Angular inspired approach
49mArchitecting Blazor applications – An Angular inspired approach
51mHands-on Development Experience Using wasm Blazor
16mFull stack web in .NET 8 with Blazor
57mRunning Blazor in production, lessons learned
01h 07mClean Architecture with .NET MAUI, Blazor, and ASP.NET Core
46mWhat's New in ASP.NET Core 8 and Blazor 8
01h 02mDeveloping Reusable Components for Blazor WASM