.NET to run in WASMEdge

[VenkateshSrini]

Is your feature request related to a problem? Please describe.

At present blazor runs in browser and can the blazor components can be embedded in mobile apps. The feature request is that can Blazor run in environment like WasmEdge (https://github.com/WasmEdge/WasmEdge). If that is the case then if we can port Kestrel also to Blazor runtime or much more a light weight version, then we could run API applications using WASMEdge. This will be much more light weight than containers. There are usecases where the same is possible using Rust runtime. Please see the article
https://www.infoq.com/articles/webassembly-dapr-wasmedge/?utm_source=email&utm_medium=Web-Development&utm_campaign=newsletter&utm_content=11162021.

Describe the solution you'd like

Blazor should be able to run in WASMEDGE. Then this can be used like desktop application and also light-weight runtime for hosting API.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[danroth27]

@lewing

[ghost]

Tagging subscribers to this area:
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Is your feature request related to a problem? Please describe.

At present blazor runs in browser and can the blazor components can be embedded in mobile apps. The feature request is that can Blazor run in environment like WasmEdge (https://github.com/WasmEdge/WasmEdge). If that is the case then if we can port Kestrel also to Blazor runtime or much more a light weight version, then we could run API applications using WASMEdge. This will be much more light weight than containers. There are usecases where the same is possible using Rust runtime. Please see the article
https://www.infoq.com/articles/webassembly-dapr-wasmedge/?utm_source=email&utm_medium=Web-Development&utm_campaign=newsletter&utm_content=11162021.

Describe the solution you'd like

Blazor should be able to run in WASMEDGE. Then this can be used like desktop application and also light-weight runtime for hosting API.

Author:	VenkateshSrini
Assignees:	-
Labels:	untriaged, area-VM-meta-mono
Milestone:	-

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Is your feature request related to a problem? Please describe.

At present blazor runs in browser and can the blazor components can be embedded in mobile apps. The feature request is that can Blazor run in environment like WasmEdge (https://github.com/WasmEdge/WasmEdge). If that is the case then if we can port Kestrel also to Blazor runtime or much more a light weight version, then we could run API applications using WASMEdge. This will be much more light weight than containers. There are usecases where the same is possible using Rust runtime. Please see the article
https://www.infoq.com/articles/webassembly-dapr-wasmedge/?utm_source=email&utm_medium=Web-Development&utm_campaign=newsletter&utm_content=11162021.

Describe the solution you'd like

Blazor should be able to run in WASMEDGE. Then this can be used like desktop application and also light-weight runtime for hosting API.

Author:	VenkateshSrini
Assignees:	-
Labels:	arch-wasm, untriaged, area-VM-meta-mono
Milestone:	-

[mdg215199]

Any update on this?

[lewing]

closing this in favor of wasi support tracking #65895

[VenkateshSrini]

The issue is #65895 is also closed. So are we saying that even in .NET 8 there is no support for WASI

[lewing]

The issue is #65895 is also closed. So are we saying that even in .NET 8 there is no support for WASI

#65895 is not closed, it is a tracking issue for the work we are doing and it points a list of PRs that have already landed in .NET 8. We don't have a fixed timetable on delivering full WASI support but it is an area of active development.