dotnet-wasi-sdk VS hippo

https://github.com/SteveSandersonMS/dotnet-wasi-sdk (compile to wasi)

Why not add .net to the list?

https://github.com/SteveSandersonMS/dotnet-wasi-sdk

The experimental SDK is published here and the SDK is really simple to use. It is published as a NuGet package and all you need to do is add the package to your .NET project. That's it... the SDK hooks into the build pipeline and produces the single .wasm we need. It simply compiles the .NET app to Wasm using the dotnet build command.

You might be able to use https://github.com/SteveSandersonMS/dotnet-wasi-sdk

You may laugh, but a few years ago all those guys who sold us (some of? us - me anyway) on Kubernetes evidently got bored with it, and now they're all building a Hippo Factory[1]. And it's actually really good. This is the current timeline!

[1] https://docs.hippofactory.dev/

WebAssembly (Wasm) is something that the Cloud Native Advocacy team has been exploring. It has been around for a few years and has mostly been used within browser-based applications. There are many blog posts on what makes WebAssembly an ideal target for running applications (e.g., smaller footprint with .wasm files compared to containers, code isolation, and sandboxing). My colleague Steven Murawski wrote a blog series on getting started with hosting Wasm apps on an emerging PaaS platform called Hippo which is developed by folks at Fermyon. In Part 1 of the series, he introduces topics and define some of the acronyms like "Wagi" and "WASI". He also introduced a runtime called Wasmtime which implements the WebAssembly System Interface (WASI) standard. This article will walk you through how Steven and I went about getting a .NET console app running as a Wasm app on the Wasmtime runtime in a Dev Container. The .NET console app produced in this article has also been contributed as a csharp template in the yo-wasm repo which is also maintained by Fermyon; so you can quickly test it out for yourself later.