hi
Try using AddDataMigrationEnvironment on your DbMigrator project.
https://github.com/abpframework/abp/blob/dev/templates/app/aspnet-core/src/MyCompanyName.MyProjectName.DbMigrator/DbMigratorHostedService.cs#L31
hi
> abp clean
> dotnet build
> abp bundle
hi
Did you run the abp bundle on your blazor wasm project?
hi
Can you share a simple project? liming.ma@volosoft.com
You can also use a hacker way to solve problems temporarily:
Refresh the current page in your Index page and pass a parameter to the Index to prevent unlimited loop refresh.
You can register this event in any component to listen to the successful login or logout event.
If you have customized the menu rendering component in your project, please re-render it in the ApplicationConfigurationChanged.
eg:
I see that a new ApplicationConfiguration request has been sent, but your menu has not been re-rendered.
hi
Please add below to your Index page:
[Inject]
protected ApplicationConfigurationChangedService ApplicationConfigurationChangedService { get; set; }
protected override async Task OnInitializedAsync()
{
ApplicationConfigurationChangedService.Changed += ApplicationConfigurationChanged;
}
private async void ApplicationConfigurationChanged()
{
// Check currentUser and other info here.
// Write info to logs.
await InvokeAsync(StateHasChanged);
}
