Yes, we did same for the Microservice example solution:
https://github.com/abpframework/abp-samples/blob/master/MicroserviceDemo/gateways/BackendAdminAppGateway.Host/BackendAdminAppGatewayHostModule.cs#L125-L137
Hi @apoorva.lele,
First of all, mixing JavaScript code with Blazor is not a good idea. The problem you see is just beginning. You may have more problems later. When we've implemented the Lepton Theme to Blazor, we dropped all the JavaScript code and re-written it as Blazor components with C# to be a native Blazor Theme.
OnAfterRenderAsync seems should work. As you said this is a general Blazor problem, it would be better to ask on Stackoverflow. I would want to help you on that, however, I haven't tried such a thing before, sorry.
Hi @apoorva.lele,
Themes are distributed as NuGet packages. In this way, you will be able to upgrade it whenever we release a new version. The NuGet package for the Lepton Theme is Volo.Abp.AspNetCore.Components.WebAssembly.LeptonTheme. You can find it as a package reference in the *.Blazor.csproj file of your solution.
App.razor is located inside the theme (in the Volo.Abp.AspNetCore.Components.WebAssembly.LeptonTheme package for this case). So, it is not in your solution and you can not directly manipulate it.
If you have a Business or Enterprise license, you can download the source code of the Lepton Theme to investigate its content. But, if you don't want to use the Lepton Theme, then you don't need that. In this case, you should implement your own theme. In this case, it would be a good feedback for us if you tell why you prefer the Metronic Theme overthe Lepton Theme?
Anyway, creating a theme is not a complex thing. Just documented the Theming for the Blazor UI: https://docs.abp.io/en/abp/4.0/UI/Blazor/Theming (this is for v4.0 that is in preview release: 4.0.0-rc.3).
We also documented the Basic Theme (https://docs.abp.io/en/abp/4.0/UI/Blazor/Basic-Theme). The Basic theme is the most minimalist theme based on plain Bootstrap and is a perfect starting point to create a new theme. You just download its source code, change local project references to nuget package references in its project (and vice verse for your own application). The document has the manual installation steps too. When you do that, remember to remove the Lepton Theme NuGet package.
You can then change however you want. Copy Metronic files into your solution, implement the menu and other layout elements. It is not different than doing it for a regular Blazor application. You don't need to get support for it since it has nothing related to the ABP Commercial anymore.
While creating a new theme is simple, implementing all the theme features is really time consuming. This is not because of the ABP. It would be same hard if you start from a plain Blazor application and try to fully implement the Metronic. This is one of the main benefits of the ABP Commercial: We did it for you :) If you haven't a really good reason, I suggest to continue with the Lepton Theme. We will be adding new layouts and styles in the future.
Auth Server is not a microservice (that servers the tenant management API). It is the authentication server. We add AppContract to it since TenantManagementAppContracts package contains the permission definitions related to the tenant management. Auth Server needs to know all the permissions.
Hi,
Microservice: Which Saas Packages to include in the service
This is explained in the document as the following:
Gateway: Which Saas Packages to include in the Gateway Application
This is explained in the document as the following:
UI Application: Which Saas Packages to include in the UI Application
This is explained in the document as the following:
If your UI is angular, then you only need to add the related NPM package (@volo/saas)
This is the package distributon. But, every microservice solution is unique. Adding packages is only the beginning. You need then configure the authentication, gateway and other parts of your solution. You need to understand all the aspects and build your own solution. This is why https://docs.abp.io/en/abp/latest/Best-Practices/Module-Architecture document is essential.
I hope this helps at the beginning :)
Thanks a lot @alexandru-bagu for your great contribution. It is already documented: https://docs.abp.io/en/abp/3.3/Application-Services#working-with-streams Closing this question.
Closing this. See https://github.com/abpframework/abp/issues/5269#issuecomment-705567350
DevExpress Blazor also uses bootstrapper
This is a good thing, so it should properly work within the ABP Commercial startup template. I don't think DevExpress Blazor integrates to the Blazorise. They are different libraries. And they don't need to integrate. You can use them side by side. Didn't try DevExpress Themes. But first try to implement and use it. If you need to help on theming, we check if that's feasable.
Hi @geffzhang,
Thanks for trying the Blazor UI. It is an early preview yet. We haven't tried to integrate to Devexpress components. However, it should be possible. Did you try to install and use it just as they've documented? If you have problems, we help you. Early feedback is valuable. Thanks.
We will be planning it. I suppose the Angular UI should be more straightforward.
