can you detail what you did and what's the current error?
I guess you'll also get this in the community version. The reason is probably "Tree Shaking" is not workng as expected in Blazor. And there are reflection usages in the ABP framework. Due to the use of reflection, it just cannot make a stable tree shaking. https://github.com/dotnet/aspnetcore/issues/28546
Until Microsoft fixes this, we can disable tree-shaking temporarily.
this happens to many of us :)
modifying the current source-code should be last option because you'll loose updating it from NuGet way.
These docs explain how to customize the existing Blazor pages:
https://docs.abp.io/en/abp/latest/UI/Blazor/Customization-Overriding-Components https://docs.abp.io/en/abp/latest/UI/AspNetCore/Customization-User-Interface
Check out my post => https://support.abp.io/QA/Questions/671/ABP-Suite-throws-Cannot-read-the-template-VoloAbpCommercialSuiteTemplatesTemplatesXXXX#answer-4bc69b9f-01b0-dab5-2387-39f96e495eb9
ABP Suite is an engine to generate CRUD pages according to your solution version. It reads from the templates and generates code into your application. On the other hand, it doesn't store the templates, because there are too many ABP application versions and each version has a different template base. The templates are located in your solution.
ABP Suite version and your ABP version must be the same. If not you will get "Cannot read the template ..." error. Sometimes after upgrading to a newer version, old version DLLs remain in the output directory of the project. To solve it; close Visual Studio or Rider and delete all BIN & OBJ folders.
How can I solve this problem
hi that's a good progress. I just want you to take a look at my this post https://support.abp.io/QA/Questions/626/Bugs--Issues-v4X#answer-f02d209c-0bb8-e1bd-a4d6-39f940b19df6
the v4.0.0 has an issue on generating Angular code, this is realated to a change in @angular-devkit/schematics. it's already fixed in v4.0.1 but it'll be released next week.
thanhvl1@fsoft.com.vn we haven't got any feedback about not showing API endpoints in Swagger. This might be related to misconfiguration of module dependencies. You can create a new question as this might be related with your project. Also you can send us your project.
@christianharo clear your browser cookies to solve Tenant not found issue. The customers will never see this issue because you'll never delete the tenant. But in your development environment, you drop your database or delete the test tenants. So it's just a development time issue.
