-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NavigationManager Exception on Static Server Rendering #3927
Comments
exact same issue as #3909 - closing as this is a Blazor issue within Visual Studio which is logged here: dotnet/aspnetcore#53996 |
@sbwalker maybe we should keep one of these open so that we don't get repeated issues? |
I tried to change the method to async to avoid the exception, please check whether it can be merged, thx. |
Fix #3927: change to async method to avoid the exception.
Revert "Fix #3927: change to async method to avoid the exception."
Re-opening so that we have a record of this known Microsoft Blazor issue |
@zyhfish you can try this suggestion: dotnet/aspnetcore#53996 (comment) |
The error is in the AdminContainer.razor file in the Theme folder, line 27 when the NavigatorManager.NavigateTo method is called, it throw a ASP Exception. It happens ever a windows is closed (in the same way). |
@jaruiz1961-ual this is a known problem when running Static Blazor in the Visual Studio debugger - see dotnet/aspnetcore#53996 |
Created a new module.
Clicked the [x] code was halted.
The text was updated successfully, but these errors were encountered: