Architecting Blazor applications – An Angular inspired approach
summary
Blazor apps follow Angular-inspired specifics: a feature-based folders layout plus Core and Shared folders, split components into Razor markup and code-behind partial classes, and use Parameter properties and EventCallback for parent/child communication with a container/presentation pattern. Demo is a server-side Blazor university social network; services use HttpClientFactory and an AppState service. Micro front-ends appear via Razor Class Libraries packed as a local NuGet, stitched in Program.cs, and the demo component renders successfully in the host app.
AI-written summary · about
chapters (11)
- 0:00Start
- 7:21Options for organizing code
- 10:35What's the correct way?
- 12:13The "Core" folder
- 12:58The "Shared" folder
- 19:31Inline component type
- 21:19Code behind component types
- 22:37Use code behind components
- 26:47Parameters
- 30:14Container presentation pattern
- 38:18Micro Frontends with Blazor
related talks
53mArchitecting Blazor Applications: An Angular inspired approach
16mFull stack web in .NET 8 with Blazor
49mArchitecture tips for hybrid apps with .NET MAUI and Blazor
51mHands-on Development Experience Using wasm Blazor
01h 07mClean Architecture with .NET MAUI, Blazor, and ASP.NET Core
01h 03mState management in Blazor
54mBuilding applications with Angular and ASP.NET Core
42mState Management in Blazor Apps