navigationManager.NavigateTo Runtime Error in .Net9. (works in .NET8) Utilizing MudBlazor Template with Authentication

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:I’m unable to use this version]

1. Create a MudBlazor Solution utilizing their template (Ensure you select Authentication).

2. Register a User. When it redirects you to the Email Confirmation Page it will crash in .NET9. It works in . NET8.

NavigationManager is a .NET class and not related to MudBlazor based on my understanding.

Thank you

---

Original Comments

Feedback Bot on 12/9/2024, 06:08 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Peter A. Weinwurm on 12/23/2024, 08:38 PM:

Any status updates in regards to this? Thank you

Kim Campbell on 1/10/2025, 07:32 AM:

Hello!
You’re right, NavigationManager is a .NET class. As for the crash, MudBlazor’s templates are still being updated for .NET 9. There might be existing issues or compatibility gaps. Have you considered reverting to .NET 8 until the updates stabilize in .NET 9?

Meanwhile, you might share this issue on MudBlazor’s GitHub page; the community and maintainers can often provide timely fixes and workarounds. It’s frustrating when these things derail your progress, but hang in there!

Peter A. Weinwurm on 1/21/2025, 02:01 AM:

Thanks Ajay. I appreciate your response.

Feedback Bot on 3/7/2025, 03:27 AM:

We detected that this issue hasn’t received a lot of activity, votes, or comments in the past 90 days. Based on this, the issues severity and affected area, it’s my experience that this issue is unlikely to get fixed. To improve the situation, consider following best practices for quality problem reports, and giving us more details on how this issue is impacting you.We detected that this issue hasn’t received a lot of activity, votes, or comments in the past 90 days. Based on this, the issues severity and affected area, it’s my experience that this issue is unlikely to get fixed. To improve the situation, consider following best practices for quality problem reports, and giving us more details on how this issue is impacting you.

Peter A. Weinwurm on 3/7/2025, 03:44 PM:

The issue is resolved and can be closed.

---

Original Solutions

Peter A. Weinwurm solved on 1/11/2025, 03:56 PM, undefined votes:

Hi Kim,

The error is gone and the issue is resolved but I don’t know how. I am running the latest VS version 17.12.3 which was released on Dec 3.

Is it possible this got patched with a Windows Update?

Thank you

Ajay Tandon solved on 1/20/2025, 03:21 PM, undefined votes:

This issue is resolved in dotnet 9.0.1.

The reason that it worked for you on Dec 3rd (version 17.12.3) is that you must have unticked ‘Break when this exception type is user unhandled’.

If you see this issue again make sure you upgrade to dotnet 9.0.1 and it will not happen as the regression, in Navigation Manager, from dotnet 8.0 has been fixed.