While Blazor Runtime is Wasm, Oqtane are not stable.

[Line4GitHub]

While Blazor Runtime is Wasm, Oqtane are not stable.

[sbwalker]

@Line4GitHub is it possible for you to provide some specific examples where you encountered instability? It would also be helpful to understand which version of Oqtane/.NET you are using.

[Line4GitHub]

If ReInstall Oqtane 2.3 with Oqtane.Framework.2.3.0.Install.zip, Then Install Blog module for Oqtane version: 1.0.3 with Module Management.
Then set Blazor Runtime to Webassembly.
The blog content only 1st time not disappear, when edit.

[sbwalker]

@Line4GitHub I assume you mean Oqtane 2.3.1 - as Oqtane 2.3.0 had a fairly major bug related to AntiForgeryTokens which required the publication of a 2.3.1 release almost immediately.

It sounds like you are experiencing instability with third party modules installed in Oqtane when running on WebAssembly. For 2SXC you would need to contact the provider of the module to determine if they are aware of the issues you are experiencing. The Blog module is not part of the Oqtane framework - so it would need to be investigated separately. Are you having any issues with the Oqtane framework itself when running on WebAssembly ( ie. unrelated to third party modules )?

[Line4GitHub]

Thank you very much for your reply!
Now there is no any issues with the Oqtane framework itself when running on WebAssembly!
Thank you very much for your reply!

[sbwalker]

One of the challenges with Blazor WebAssembly is ts dependency on the linker and the “magic” which happens under the covers when you publish a release. The linker removes classes and methods from the core (System.*) libraries that it thinks the application isn’t using. So, if the linker sees 10 assemblies in the app, and doesn’t see anyone calling string.Replace, the linker will remove the Replace method from System.String. However, if the application dynamically loads up an 11th assembly that does call string.Replace, the application is going to crash. However it is also important to understand why the linker removes methods - it does this to optimize the code that is downloaded to the browser to ensure the application performs well on the first load.

[Line4GitHub]

Thank you very much for your detailed explanation.