Usage of CoreRT with browser-wasm RID

[kant2002]

With introduction of browser-wasm in dotnet/runtime#34940 I have a question. From what known, standard libraries will ship with native libraries with .a extension. These libraries will be injected into ILC pipeline to provide native support. At least @yowl said so on Gitter.

I'm interested in tap into that infrastructure and Preview 5 at least has support for browser-wasm, but unfortunately dotnet publish -r browser-wasm failing with

error NETSDK1084: There is no application host available for the specified RuntimeIdentifier 'browser-wasm'

I did quick search in Runtime repo, but did not found discussions regarding AppHosts in WASM. Also I do not understand how it can be implemented in first place. Anyway.

I imagine that building of WASM executables in CoreRT can be done using dotnet publish -r browser-wasm. Does that looks like right direction?

[jkotas]

The browser-wasm support in the .NET SDK is specialized for ASP.NET blazor apps.

I assume that you have tried this on a "hello world" app. Is this correct? I do not think that it is possible to publish a standalone browser app (w/o blazor) today. You may want to open an issue about it in SDK repo to discuss the plans.

dotnet publish -r browser-wasm

That sounds fine to me.