NET 6 Wasm Prerendered with persist state component vs HybridBlazor about hybridblazor HOT 5 CLOSED

Hi,

PersistentComponentState is used in

Prerendering enabled too

In general, the whole idea of the project is to have interaction when WASM is not loaded yet.

from hybridblazor.

Ok, thanks for replies.

from hybridblazor.

Hi, I have one question more. When blazor is using WebAsssemblyPrerendered then PersistentComponentState avoided execute ForecastService.GetForecastAsync when switched from static files to WASM.
In your solution PersistentComponentState works only for server mode. When page is switched to WASM then ForecastService.GetForecastAsync is invoked again.
Does it is possible to persist state with PersistentComponentState between server and wasm in your solution?

from hybridblazor.

Surely this is possible, but it is hardly easy to do, I have not tried it. I don't understand why use WebAssemblyPrerendered because prerendering will already be done in ServerPrerendered mode.

You can also look towards the https://github.com/servicetitan/Stl.Fusion library if you need to manage complex state

from hybridblazor.

Thanks for help. Btw. I don't want to use WebAssemblyPrerendered. I puted this as example to compare with your solution.

from hybridblazor.