Clean Architecture with .NET MAUI, Blazor, and ASP.NET Core
summary
Clean Architecture applied to a .NET full stack: an ASP.NET Core API, shared DTOs and generated API clients (NSwag), a .NET MAUI mobile app that authenticates and shows editable to‑do lists, and an Angular (planned Blazor) web UI. Multi‑targeting lets view models run unit tests on .NET 8, and most backend and UI tests pass locally. Warnings: over‑engineered client packages, deep inheritance traps — favor composition and multi‑targeted MAUI view‑model tests to keep refactoring safe.
AI-written summary · about
chapters (15)
- 0:00Full stack .NET intro
- 3:58Evolution of .NET
- 7:12Clean architecture principles
- 12:36Implementing clean architecture
- 22:34Demo: .NET MAUI app
- 32:18Over-engineering pitfalls
- 37:19Deep hierarchies vs composition
- 49:47Avoiding YAGNI
- 51:55Preventing Inception in UI
- 54:44The pit of success
- 56:49Clarity over brevity
- 58:35WET vs DRY
- 1:00:23Keeping it fun
- 1:02:28Enterprise code sharing
- 1:04:14Resources & closing
related talks
50mClean Architecture with ASP.NET Core 2.2
49mArchitecture tips for hybrid apps with .NET MAUI and Blazor
01h 02mImplementing the Clean Architecture in .NET Core
47mUnleashing Clean Architecture in .NET 8
53mArchitecting Blazor Applications: An Angular inspired approach
49mArchitecting Blazor applications – An Angular inspired approach
34mHybrid Web and Desktop apps with .NET MAUI and Blazor
49mArchitecting Blazor applications – An Angular inspired approach