Finalize the workload-id and any aliases for installing blazorwasm-aot and/or browser-native workloads and aliases therein. Preview4 shipped with microsoft-net-sdk-blazorwebassembly-aot the inital runtime manifest shipped with microsoft-net-runtime-browser-native and we reverted it to microsoft-net-sdk-blazorwebassembly-aot after objections. Since these names are surfaced in the cli for installing non-abstract workloads, and we can trivially a workload alias I think we should review these names and ideally setting on shorter versions.
dotnet workload install microsoft-net-sdk-blazorwebassembly-aot is a lot to type
Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.
Issue Details
Finalize the workload-id and any aliases for installing blazorwasm-aot and/or browser-native workloads and aliases therein. Preview4 shipped with `microsoft-net-sdk-blazorwebassembly-aot` the inital runtime manifest shipped with `microsoft-net-runtime-browser-native` and we reverted it to `microsoft-net-sdk-blazorwebassembly-aot` for after objections. Since these names are surfaced in the cli for installing non-abstract workloads, and we can trivially a workload alias I think we should review these names and ideally setting on shorter versions.
Finalize the workload-id and any aliases for installing blazorwasm-aot and/or browser-native workloads and aliases therein. Preview4 shipped with
microsoft-net-sdk-blazorwebassembly-aot
the inital runtime manifest shipped withmicrosoft-net-runtime-browser-native
and we reverted it tomicrosoft-net-sdk-blazorwebassembly-aot
after objections. Since these names are surfaced in the cli for installing non-abstract workloads, and we can trivially a workload alias I think we should review these names and ideally setting on shorter versions.dotnet workload install microsoft-net-sdk-blazorwebassembly-aot
is a lot to type