Catch-All routing with Blazor/OrchardCore De-Coupled CMS.

[ApacheTech]

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.

[ApacheTech]

This is the page I would like to have work.

@page "/{*Slug}";
@if(_contentItem is null)
{
    <StatusCodeErrorPage StatusCode="@(404)" />
}
else
{
    <DynamicComponent Type="_contentItemType" Parameters="_parameters" />
}

@code {
    private Dictionary<string, object> _parameters = [];
    private ContentItem? _contentItem;
    private Type? _contentItemType;

    [Parameter]
    public string Slug { get; set; }

    [Inject]
    private IOrchardHelper Orchard { get; init; }

    protected override async Task OnParametersSetAsync()
    {
        _contentItem = await Orchard.GetContentItemBySlugAsync(Slug);
        if (_contentItem is null) return;
        _parameters["ContentItem"] = _contentItem;
        _contentItemType = GetType().Assembly
            .GetTypes()
            .Where(p => !p.IsAbstract && p.IsSubclassOf(typeof(CsmHostedComponentBase)))
            .SingleOrDefault(p => p.Name == _contentItem.ContentType);
        StateHasChanged();
    }
}

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.

[ApacheTech]

Another problem I've found. Because you can't exclude segments, the next obvious thing would be to have multiple whitelisted segments, and then your slug.

@page "/prefix-1/{*Slug}";
@page "/prefix-2/{*Slug}";
@page "/prefix-3/{*Slug}";
@inherits RoutedComponentBase;
@code {
    [Parameter] public string? Slug { get; set; }
}
<ContentRouter Alias="@NavigationManager.ToBaseRelativePath(NavigationManager.Uri)" />

However, now, going from /prefix-1 to /prefix-2 via a NavLink does not, and so far as I can tell, cannot issue any kind of page update, because Slug hasn't changed. I've have tried multiple ways of forcing a refresh on this, and nothing has worked. You can't force render via NavLink. I even tried disposing the entire component after it's rendered. Nothing works at all.

Is there any way to make this transient, so that it treats the parameters as changed, every single time?