- ABP Framework version: v6.0.1
- UI type: Blazor Web Assembly
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace:
- Steps to reproduce the issue:" Just use ABP Suite to generate a new solution Blazor wasm app template with a public website, no CMS Kit, LeptonX theme, disable multi-tenancy, add chat module.
Hello!
Unfortunately no tutorial or documentation really helped to actually implement the chat module in a Blazor wasm app, so please don't send me to documentation or the latest tutorial in APB Community.
Can the Support Team provide a sample Blazor wasm app template with a Blazor public website in which the chat module is actually working in a non-multitenant environment?
The chat module should be enabled by default. There's no need to actually enable chat for a tenant if I am not using multitenancy. Nor SaaS editions, etc.
Steps I did:
Create a Blazor WASM app from ABP Suite, LeptonX theme, ver. 6.0.1, non-tiered.
Went into *.Domain.Shared and disable multitenancy.
From ABP Suite added Chat module as package.
Opened the solution and tried to run and got errors to AbpBundlingOptions. You can see them if you reproduce the steps.
Solved errors, created an user. As its a non multi-tenant environment, I can't assign chat permissions.
Opened the blazor website, opened the public website: no chat icon.
This is the solution as it was generated by ABP Suite and after added the chat module as packaged:
https://github.com/RelevanceRo/TestChatModule.git
Please help me understand how to implement the Chat Module in a full blazor environment with no SaaS / multitenancy.
PS:
A few suggestions and questions:
Why the public website is an MVC Razor pages app if the template is Blazor wasm? Is it planned to update the ABP Suite to generate the public website with the same tech stack as the back-end app?
ABP Suite should have an options to disable SaaS / Tenancy from the UI. The SaaS / Tenancy is really a small niche of application developed with ABP Framework.
Why after I disable multitenancy I still get in the Administration menu SaaS / Tenant sections? How can I actually remove completely those sections from the administration menu?
3 Answer(s)
-
0
Hi @ccernat, We are sorry for the late response.
First of all, please delete this github repository. Your nuget api key is exposed there https://github.com/RelevanceRo/TestChatModule/blob/master/NuGet.Config This is not allowed.
Why the public website is an MVC Razor pages app if the template is Blazor wasm? Is it planned to update the ABP Suite to generate the public website with the same tech stack as the back-end app?
Blazor wasm is for single-page backend applications and not suitable for public websites.
ABP Suite should have an options to disable SaaS / Tenancy from the UI. The SaaS / Tenancy is really a small niche of application developed with ABP Framework.
We may consider disabling multi-tenancy on project creation. I'll create an issue about that.
Why after I disable multitenancy I still get in the Administration menu SaaS / Tenant sections? How can I actually remove completely those sections from the administration menu?
You have to remove the Saas module from the solution (csproj & module.cs files).
We'll reply the question related with Chat module in a short time.
-
0
Hi @ccernat, We are sorry for the late response.
First of all, please delete this github repository. Your nuget api key is exposed there https://github.com/RelevanceRo/TestChatModule/blob/master/NuGet.Config
This is not allowed.Why the public website is an MVC Razor pages app if the template is Blazor wasm? Is it planned to update the ABP Suite to generate the public website with the same tech stack as the back-end app?
Blazor wasm is for single-page backend applications and not suitable for public websites.
ABP Suite should have an options to disable SaaS / Tenancy from the UI. The SaaS / Tenancy is really a small niche of application developed with ABP Framework.
We may consider disabling multi-tenancy on project creation. I'll create an issue about that.
Why after I disable multitenancy I still get in the Administration menu SaaS / Tenant sections? How can I actually remove completely those sections from the administration menu?
You have to remove the Saas module from the solution (csproj & module.cs files).
We'll reply the question related with Chat module in a short time.
My bad. Repo deleted.
Tks for noticing.
-
0
hi ccernat
Please invite me to your Github repo.
https://github.com/maliming
