-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Open
Labels
Cost:MWork that requires one engineer up to 2 weeksWork that requires one engineer up to 2 weeksPriority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutUser StoryA single user-facing feature. Can be grouped under an epic.A single user-facing feature. Can be grouped under an epic.arch-wasmWebAssembly architectureWebAssembly architecturearea-Meta
Milestone
Description
Developers would like to be able to easily consume NuGets for use in browser-wasm applications. NuGets which consist of managed libraries only are generally supported as long as they target net5.0+ and avoid APIs marked with the [UnsupportedOsPlatform("browser")] attribute. We need to go beyond that and support NuGet packages that include also native/unmanaged code targeting browser-wasm RID.
Work Items
- NuGet Packaging
- Document structure expectations
- ABI versioning
- Source builds
- Tooling
- Tooling installation (emscripten SDK)
- Expose version requirements with LTS considerations
- Run pinvoke generator on NuGet assemblies
- Relink runtime with native code in build and publish ([wasm] Add support for native relinking after Build, and AOT after publish #57556)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Cost:MWork that requires one engineer up to 2 weeksWork that requires one engineer up to 2 weeksPriority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutUser StoryA single user-facing feature. Can be grouped under an epic.A single user-facing feature. Can be grouped under an epic.arch-wasmWebAssembly architectureWebAssembly architecturearea-Meta