AspNetCore `net8.0` - Blazor {*CatchAll} route overrides MVC AdminController route
I'm using a Blazor8 with OrchardCore as a de-coupled CMS. I want
/admin*
to be routed by Orchard, and the rest to be routed by Blazor.
Using this as a basic working example: https://github.com/ApacheTech/BlazOrchard
If I have a page with @page "/{*Slug}";
, I want to give priority to /admin
to run through the MVC Area controller. It seems that Blazor strips all power away from MVC to route itself. I want Blazor to be the fallback.GitHub
GitHub - ApacheTech/BlazOrchard: This repo gives an example of how ...
This repo gives an example of how to set up a solution to run an OrchardCore Decoupled CMS, with a Blazor Web App front-end. - ApacheTech/BlazOrchard
1 Reply
There is no manual mapping here, other than Blazor. Would I need to map the admin area separately. If so, in which part?
This is the page I would like to have work.
Then all my components would be at
/Components/ContentTypes/{nameof(ContentType)}.razor
, and inherit from CmsHostedComponentBase
that supplies access to the helper, and other injected tools, as standard.
But, using this, calls to /admin
result in the 404 component showing. MVC is ignored. I thought that catch-all routes were supposed to have lowest priority.