Open gthvidsten opened 3 months ago
Workaround: You can specify the assembly in <Route AdditionalAssemblies=....>
Note that you need this and AddAdditionalAssemblies(...) in order to get both internal navigation to work (from one page to another) and also initial navigation (first page or user hits reload).
Is there an existing issue for this?
Describe the bug
This might be related to #46980. Pages defined in a RCL that has been added as an additional assembly to
.MapRazorComponents<>()
, using.AddAdditionalAssemblies()
are not reachable if the router has@rendermode="InteractiveServer"
.Expected Behavior
Pages defined in the RCL should be reachable regardless of
@rendermode
Steps To Reproduce
Interactive render mode = Server
andInteractivity location = Per page/component
.@page "/custompath"
/custompath
is reachable@rendermode=InteractiveServer
to<Routes />
inApp.razor
/custompath
is not reachable (It enters the<NotFound>
section in the<Router>
if it exists)Exceptions (if any)
N/A
.NET Version
8.0.303
Anything else?
ASP.NET Core version: 8.0.7 IDE: Visual Studio Professional 2022 (64-bit) 17.10.4
dotnet --info
: