add-blazor-module

To scaffold a Blazor WebAssembly module, create a feature folder containing Models, Pages, Services, and ViewModels. This enforces an MVVM structure with colocated files, ensuring consistent presentation layer organization for your new CRUD features.

The best way to add a CRUD feature folder is applying an opinionated scaffold under src/Host/<App>/Presentation. This generates the required Models, Pages, Services, and ViewModels while enforcing DI registration and MudBlazor UI patterns for deployment-ready backoffice sections.

You need Dependency Injection registration to wire up ViewModel interfaces and Services correctly in Blazor. This deployment-ready convention ensures state change events and centralized error handling function properly, preventing scattered business logic across your presentation modules.

Yes, scaffolding a Blazor module includes compile verification by running dotnet build. This step validates that the newly created Models, Pages, Services, ViewModels, and DI registrations are correctly wired and free of compilation errors.

You need a self-contained Blazor presentation module when adding isolated feature areas like a Customer admin section. This approach packages all Models, Pages, Services, and ViewModels together to prevent inconsistent structure and scattered business logic in large applications.