Is it part of the roadmap to be able to handle wasm-files as you can with dll-files today, in regards to running a .NET application and be able to:
Load a wasm-file (written in another language)
Use reflection to find something implementing an "interface" (or an "export")
Create an instance of that "class" and call methods (or calling static functions)
I could see multiple use cases for that functionality. Creating a C# host that allows for externals to implement some specification and dynamically load the third-party modules/wasm-files.
If not possible using the .NET runtime, then with the application compiled as a wasm-application and dynamically loading and using wasm-files written in other languages.
Hi
Is it part of the roadmap to be able to handle wasm-files as you can with dll-files today, in regards to running a .NET application and be able to:
I could see multiple use cases for that functionality. Creating a C# host that allows for externals to implement some specification and dynamically load the third-party modules/wasm-files.
If not possible using the .NET runtime, then with the application compiled as a wasm-application and dynamically loading and using wasm-files written in other languages.
Best regards db