aspnetcore: Dotnet 9.0 scaffolding no longer works - errors when doing NavigationManager.NavigateTo in Create.razor
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
Perform the Dan Roth tutorial in https://www.youtube.com/watch?v=ZN-CcfEY3Z8
At 5:39 when the Create button is pressed, a failure happens in
NavigationManager.NavigateTo("/movies");
This is the failure in VS2022 17.12:
Microsoft.AspNetCore.Components.NavigationException HResult=0x80131500 Message=Exception_WasThrown Source=Microsoft.AspNetCore.Components.Server StackTrace: at Microsoft.AspNetCore.Components.Server.Circuits.RemoteNavigationManager.NavigateToCore(String uri, NavigationOptions options) at Microsoft.AspNetCore.Components.NavigationManager.NavigateToCore(String uri, Boolean forceLoad) at Microsoft.AspNetCore.Components.NavigationManager.NavigateTo(String uri, Boolean forceLoad, Boolean replace) at BlazorMovieCRUDDemo.Components.Pages.MoviePages.Create.<AddMovie>d__5.MoveNext() in C:\Users\ajayt\Desktop\Upgrade to dotnet 9 GA\BlazorMovieCRUDDemo\BlazorMovieCRUDDemo\Components\Pages\MoviePages\Create.razor:line 58 at Microsoft.AspNetCore.Components.ComponentBase.<CallStateHasChangedOnAsyncCompletion>d__30.MoveNext()
This is from the autogenerated scaffolding performed exactly as Dan does it.
This used to work in dotnet 8.0, but now fails in dotnet 9.0.
Additionally, my dotnet 8.0 project when upgraded to dotnet 9.0 fails here as well.
Expected Behavior
I expect this to work as it did in dotnet 8.0
Steps To Reproduce
Perform the Dan Roth tutorial in https://www.youtube.com/watch?v=ZN-CcfEY3Z8
At 5:39 when the Create button is pressed, a failure happens in
NavigationManager.NavigateTo("/movies");
This is scaffolded code in Create.razor in the MoviePages subfolder.
Exceptions (if any)
This is the failure in VS2022 17.12:
Microsoft.AspNetCore.Components.NavigationException HResult=0x80131500 Message=Exception_WasThrown Source=Microsoft.AspNetCore.Components.Server StackTrace: at Microsoft.AspNetCore.Components.Server.Circuits.RemoteNavigationManager.NavigateToCore(String uri, NavigationOptions options) at Microsoft.AspNetCore.Components.NavigationManager.NavigateToCore(String uri, Boolean forceLoad) at Microsoft.AspNetCore.Components.NavigationManager.NavigateTo(String uri, Boolean forceLoad, Boolean replace) at BlazorMovieCRUDDemo.Components.Pages.MoviePages.Create.<AddMovie>d__5.MoveNext() in C:\Users\ajayt\Desktop\Upgrade to dotnet 9 GA\BlazorMovieCRUDDemo\BlazorMovieCRUDDemo\Components\Pages\MoviePages\Create.razor:line 58 at Microsoft.AspNetCore.Components.ComponentBase.<CallStateHasChangedOnAsyncCompletion>d__30.MoveNext()
.NET Version
9.0.0
Anything else?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19 (13 by maintainers)
@guardrex For now, I think we need to do this.
@danroth27 … UPDATE: I’m going with the 8.0 framework in the 9.0 content to workaround this for now. The change is ⚡LIVE⚡ now. Temporarily use 8.0 framework (
dotnet/AspNetCore.Docs#34118). I have tracking in place to revert back to 9.0 when the problem is resolved in the framework.I know from our earlier discussion on a separate doc task that you aren’t favorable to that blaring red CAUTION note in articles 📣😬, but I really want devs to see the instruction on selecting the 8.0 framework. If they don’t see it, they’ll get rather upset when their app 💥, and it will probably result in doc issues. I’m just trying to head that off with the most noticeable notice that we have. If you want to remove or change the word “CAUTION,” I can place HTML in the article for a red alert box. 👂