Blazor Wasm server-hosted project with routing on the client

[ecaldentey]

Hello Rocky,

I would like to know if it's possible for CSLA to work in a server-hosted Blazor WebAssembly project, but where the control of page routing (App.razor), the definition of static files and JavaScripts (index.html), and the management of styles (app.css) are defined in the client project?

The architecture I currently have working is a server-hosted Wasm project with CSLA 8.2.2, but with page routing (Routes.razor), the definition of static files and JavaScripts (App.razor), and style management (app.css) on the server, and it works perfectly.

In fact, in the server project's root, I have the ActiveCircuitHandler service defined, which is loaded in the server's Program.cs and uses the ActiveCircuitState class defined in the client project. This means this architecture requires a reference from the server project to the client project, which should also be possible to implement in the architecture I need.

I need to use the architecture with control in the client project because I have some components that work with this architecture and fail when the routing is on the server, as they cannot route properly to make requests to the controller.

I look forward to your help.

Thank you.

[rockfordlhotka]

I honestly don't understand what you are asking. I don't think CSLA has anything to do with this at all - it seems like you are asking about Blazor routing and styling, which CSLA won't affect.

[ecaldentey]

Hello Rocky,

Thank you for your response. Let me try to simplify my question.

My core concern is straightforward: Is there any incompatibility with CSLA if the routing is handled entirely by the client-side (Wasm project)?

I ask because my understanding—and I may be wrong—is that CSLA does not work in a standalone WebAssembly project (without a server project). My current solution is based on the ProjectTracker example, which uses the server-hosted model.

I have been unable to find comprehensive documentation on which specific Blazor hosting architectures (of which there are several) are supported by CSLA and which are not. This is why I brought my question to the discussion group, hoping for guidance based on the community's or your expertise.

The architectural details in my previous message were my attempt to describe the specific server-hosted scenario I need to use, but my fundamental question is just about CSLA's compatibility with client-side routing.

Thank you for your time and help.

Best regards,

Esteban

[rockfordlhotka]

Oh, if you want to use the 'Blazor Standalone WebAssembly' project template to create a pure client-side app with Blazor, CSLA will work great!

In that case there is no server at all - beyond a file server used by the browser to download all the necessary files.

Normally in that case you'll use client-side JSON files or maybe Sqlite to manage your data on the client machine. CSLA supports that just fine with a local data portal.