Open Issues Need Help
View All on GitHub Lazy-loaded WASM RCL with pages does not work with Blazouter Router (missing AdditionalAssemblies) about 2 months ago
AI Summary: The user is reporting a bug where Blazouter Router does not correctly handle lazy-loaded Razor Class Libraries (RCLs) in Blazor WebAssembly applications. Unlike the default Blazor Router, Blazouter does not seem to have an equivalent mechanism to register these additional assemblies, causing pages within the lazy-loaded RCLs to fail to resolve.
Complexity:
3/5
bug enhancement good first issue solved
Blazouter brings modern, React Router-inspired routing to Blazor. It provides true nested routes, built‑in route guards, lazy loading, per-route layouts and rich transitions — all type-safe and compatible with Server, WebAssembly, and Hybrid (MAUI) hosting models.
C#
#aot#blazor#client#csharp#dotnet#guards#hybrid#lazy-loading#maui#navigation#nested#nested-routing#react-router#route-guards#router#routing#server#transitions#wasm#webassembly