Blazor / WASM with full .NET runtime

[ladeak]

Can I use any of the mentioned solutions for Balzor/WASM JS interop with the full .NET runtime (instead of mono)?

Ref: https://www.youtube.com/watch?v=tAh899Gri4E

cc. @javiercn and @maraf

As a comparison to https://github.com/microsoft/node-api-dotnet the solution in the video use WASM while the nodeAPI is more suited for electron apps?

[maraf]

Are you looking for Blazor Hybrid?
Where .NET code runs on the host process and IJSRuntime implementation calls to WebView?

[ladeak]

I am looking for the best approach to use c# libraries from JS (VS code extension). Currently I use https://github.com/microsoft/node-api-dotnet, but I really liked your demo and I wonder if I cojld/should switch. Hence wondering if the dotnet is the mono runtime or the full one.

[maraf]

There is a significant difference in these two approaches that affects the outcome.

Running on WebAssembly means there is an abstraction (WebAssembly) between the code and the executing environment / machine. This abstraction comes with a price, but on the other hand it gives portability. Whereas note-api-dotnet runs in proc on Node, using all the goodness .NET core has, but it requires a native node module and (if NativeAOT is not used) a .NET runtime on the target machine. .NET on WebAssembly is a supported product with several years of usage on various applications. It is tied to Mono runtime at the moment, because Mono runtime is much more optimal for the needs connected with WebApps / WebAssembly. Although there is community driven experiment with using Native AOT https://github.com/dotnet/runtimelab/tree/feature/NativeAOT-LLVM.

[ladeak]

Thank you for the detailed explanation and response.