Question about Rendermodes

[BrettButcher]

Can you add webassembly components to a Blazorise project that uses interactiveserver rendermode.
To make Layout work interactively you need to either use global interactive server rendermode, or use the Blazorise template, which seems to go through various hoops to avoid this.

In either case, I can't make an interactive WebAssemlbly component work.

Is that even possible? If so, is there any blog, doc, that shows how? TIA.
Brett

PS. I have a StackOverflow question that details this more. With no response so far.
StackOverflow question

[stsrki]

There shouldn't be any difference with WebAssembly components. All Blazor components should work in all render modes. The only difference is the interactivity.

Can you share the code of your problematic component?

[BrettButcher]

I will go recreate my tests. They were generated using standard templates and adding a simple 'counter' component to test the webassembly.
The Blazorise template does strange things to avoid using global interactive server rendermode. (See my stackoverflow question) and the compent I want to add is a simple 'counter' to prove the concept.
I did another test which I will recreate using the standard VS template. This more reflects the app I aant to change. Thanks

[BrettButcher]

Hi I have added a couple of GIT repositories with the server and client projects that show this:
https://github.com/BrettButcher/Test.client
https://github.com/BrettButcher/Blazor-Server-Plus-Wasm-Testing

The client app has a simple downcounter widget.
The server has blazorise set up and the render modes set to interactiveserver in the App.razor. (This is the only way I can easily make the Blazorise Layout work interactively).
The downcounter widget is setup in the Counter2 page. If you remove the rendermode from the component it works fine in interactive server mode.
With the rendermode st to webAssembly it falls over.

Any thoughts on this... I see that your own template in VS sets up the rendermode differently but I couldnt make that work with WASM either. TIA Brett

[stsrki]

I think you need to set the InteractiveAuto to mix the two modes.

[BrettButcher]

Sadly that doesn't work as then the blazorise Layout doesnt work. Being on the server side the Layout is then statically rendered.
I could of course move the layout to the Wasm client side but I am trying to avoid the large download during the first page load.

It is a real problem that the blazor layout objects can not have the rendermode assigned to they are almost always one of the first things loaded.

The other option of course being to abandon using the Blazorise Layout and use a Bootstrap menu like the Sample Templates...

[BrettButcher]

So does anyone think it is possible to get a blazorise layout running interactively without using WASM on initial load?
I think not... if not, that is ok, I will switch to a pure bootstrap/js approach... but it would have been nice to use all the blazorise theme colours...

[stsrki]

As far as I am aware, layouts cannot handle rendermode, see here https://stackoverflow.com/questions/77614553/render-mode-in-mainlayout-razor-blazor-8

You need to define it globally.

PS. Some time ago, we successfully implemented the same in the Blazorise web. So it might help you as a reference #5091
PPS. We haven't merged it due to some security concerns when running in WASM mode. But other than that, the web worked in Auto mode.

[BrettButcher]

Thank you for coming back to me...
Yes, thats right, and so far when I have set the global rendermode to InteractiveServer the Layouts work fine.

The problem comes when I want to add some Wasm components. (Clock based items that should really run on the client as they would thrash a SignalR connection.)
If I set the global rendermode to InteractiveAuto, then the Layout renders statically and doesnt run... could that be because it needs to be on both the Server AND the client? ... I'll give that a try, but suspect that because it is on the first load then the WAS download may have to happen before it runs. I'll let you know what happens.
Thanks again.