Improve workload ID naming in VS

marcpopMSFT commented 4 months ago

Today, the workloads when we insert into VS get names like wasm.tools. VS has requested that we follow a more common naming convention for this. Below is potentially the work that would be required.

Investigate whether prepending additional text would hit any file length limitations
Update arcade tooling in main to prepend microsoft.net. or microsoft.net.workloads. to the front of the workload ID when generating the VS component
optionally hide this behind a property so workloads can choose when to opt into this
work with the project system team to handle the new id names in the IPA experience (Oswaldo did this work originally, I think they have specific logic for workloads so it could be feasible but how to handle the before and after would be complex)
Investigate if the sdk missing workload logic needs to change as well (I don't think it actually does fwiw)

From Jacques: The component names have generally been quite short, e.g. wasm-tools or maui, so prepending with Microsoft.NET.Workloads should not be a problem, most of the path issues came from the packs which we resolved by having shorter names. Note that if we decide to change the component IDs, when VS upgrades from a build with the old to the new IDs and wasm tools was selected, it will end up being removed because the new catalog doesn't carry the old component and users would need to reselect the new WASM tools component

marcpopMSFT commented 1 week ago

https://github.com/dotnet/arcade/pull/15103

We'll need to flow arcade and get all workload owners to opt in to the new flag.

marcpopMSFT commented 4 hours ago

https://github.com/dotnet/sdk/pull/44198 also needs changes in emsdk, runtime, and every Maui repo that builds workloads.

dotnet / sdk

Improve workload ID naming in VS #41125