Research .NET runtime WASM module lifecycle
See original GitHub issueIt is not clear whether the .NET runtime WASM module have to be terminated and/or if it can be re-initialized.
There appears to be emscripten_force_exit
function in the module, but it throws an error:
https://github.com/Elringus/DotNetJS/blob/97647de97a9ffe0aafdc1941a947f79f9816b9d8/JavaScript/dotnet-runtime/src/wasm.ts#L25
Is someone have any related info, please let us know here.
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Issues · Elringus/DotNetJS - GitHub
Research .NET runtime WASM module lifecycle enhancement New feature or enhancement help wanted Community help is most appreciated. #22 opened on Dec 23, ......
Read more >ASP.NET Core Razor component lifecycle | Microsoft Learn
The Razor component processes Razor component lifecycle events in a set of synchronous and asynchronous lifecycle methods.
Read more >The Future of .NET with WASM | The .NET Tools Blog
Currently, there is a Wasmruntime NuGet package that contains low-level APIs for dealing with the elements of a host. These elements include an ......
Read more >An Empirical Study of Bugs in WebAssembly Compilers
This study focuses on the lifecycle of the bugs, their impacts, and the sizes of the bug-inducing inputs and bug fixes. Based on...
Read more >WebAssembly | Blazor FAQ - Syncfusion
Blazor WebAssembly can run client-side C# code directly in the browser. The Blazor application, as well as its dependencies and the .NET runtime...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s .NET runtime for wasm, which is not just for blazor, so there’s still a chance. They’ve already made a lot of progress to modularize it in .NET 6-7. And again, I’m planning to opt-out of custom runtime build by .NET 7 release, so patching it further is not desired.
Blazor certainly doesn’t exit, as it runs through the entire page lifecycle and will not change in future versions I think. So you’re better off building a version yourself.