Hi,
There seems to be very little solid documentation around the Blazor WebApp. I have gone through numerous project types now and struggle to get proper guidance on aspects like Module additions etc.
I am now moving over to the simplest of options in the hope of progressing. Within a Blazor Web, No Layer Solution...when adding a New Module via the ABP Suite, you have Blazor Server and WebAssembly. Which option is most compatible. I would imagine if WebAssembly I would need to create HTTP Controllers, whereas Server will just use the created DI?
Am I correct and when are we likely to see more Documentation and Enhancement around WebApp?
- **Template**: app-nolayers - **Created ABP Studio Version**: 1.0.2 - **Current ABP Studio Version**: 1.0.2 - **Multi-Tenancy**: Yes - **UI Framework**: blazor - **Theme**: leptonx - **Theme Style**: system - **Theme Menu Placement**: side - **Run Install Libs**: Yes - **Run Bundling**: No - **Database Provider**: ef - **Database Management System**: sqlserver - **Create Initial Migration**: Yes - **Run Db Migrator**: Yes - **Social Login**: Yes - **Use Local References**: No - **Optional Modules**: * GDPR * FileManagement * TextTemplateManagement * LanguageManagement * AuditLogging * Chat * OpenIddictAdmin - **Selected Languages**: English, Deutsch (Deuthschland) - **Default Language**: English - **Create Command**: abp new GravityPlatform -t app-nolayers --ui-framework blazor --mobile --database-provider ef --database-management-system sqlserver --theme leptonx --no-tests --without-cms-kit --dont-run-bundling -chat -file-management
1 Answer(s)
-
0
In a Blazor WebApp "No Layer" (monolithic) ABP solution, when adding a new module via ABP Suite, you are correct in your assumptions:
- If you select the "Blazor Server" option for the module, it will integrate directly with your application using dependency injection (DI). This is the most compatible and straightforward choice for a Blazor WebApp monolith, as it allows you to use services and components without needing to expose HTTP APIs.
- If you select the "WebAssembly" option, the module is designed for a client-side Blazor WebAssembly scenario. In this case, you would typically need to expose HTTP API controllers for the client to communicate with the backend, which is not necessary in a pure Blazor Server or Blazor WebApp (monolithic) setup.
For a Blazor WebApp "No Layer" solution, choose "Blazor Server" when adding modules for the most seamless integration.
Regarding documentation and enhancements for Blazor WebApp, ABP is actively evolving its documentation and features. The most up-to-date and official starting point is the "Get Started" section:
This page is regularly updated as new features and documentation become available.
If you need to add modules or extend your application, follow the standard ABP modularity approach, but always prefer the "Blazor Server" option for modules in a monolithic Blazor WebApp.
Sources:
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
