You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we have fallback options for Areas, Controllers, Pages and Files. But we can't fallback to a razor component.
In a Blazor Web App (static SSR) none of above can be used without adding their required services. And the <Router>'s <NotFound> does not work in static SSR mode. So, if there is a Pages/NotFound.razor component, I think ideally, we should have a app.MapFallbackToComponent<Pages.NotFound>() as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, we have fallback options for Areas, Controllers, Pages and Files. But we can't fallback to a razor component.
In a Blazor Web App (static SSR) none of above can be used without adding their required services. And the
<Router>'s<NotFound>does not work in static SSR mode. So, if there is aPages/NotFound.razorcomponent, I think ideally, we should have aapp.MapFallbackToComponent<Pages.NotFound>()as well.Beta Was this translation helpful? Give feedback.
All reactions