For anyone running into the same issue, you just need to inject ABP's ISettingProvider
See ABP's documentation
Thank you for the confirmation on this @liangshiwei
Excellent, that worked.
Thanks @mailiming !
Ok, thank you for confirming.
This may be the limitation of Blazor server.
Hi, for the Lepton Theme (not LeptonX), isn't the side menu loaded using MVC and not Blazor Server? From what I understand, the Blazor Server application is actually a hybrid MVC/Blazor Server app.
Thanks...
A follow up question....
In the authenticator app, the application is identified using the .NET project name <company>.<app>.Blazor, How can we customize the application name registered with the user's authenticator app?
Thanks @maliming!
I forgot about install-libs, that worked :-)
Hi @mailiming,
{
"version": "1.0.0",
"name": "my-app",
"private": true,
"dependencies": {
"@volo/abp.aspnetcore.mvc.ui.theme.lepton": "~7.4.2",
"@volo/abp.aspnetcore.components.server.leptontheme": "~7.4.2",
"@volo/cms-kit-pro.admin": "~7.4.2",
"@volo/account": "~7.4.2"
}
}
Hi @liangshiwei,
We don't recall noticing the issue when we were on versions 5 and 6, but after doing some debugging on our end, I'm thinking this may have been a problem back then as well and we just didn't notice it because our initial screen after logging in back then was less complex and we were not running in a hosted environment (local dev only).