Optional Workload Acquisition

[marcpopMSFT]

This epic covers the work to be able to acquire an optional workload

• Given the npkg and manifest from the workload owner, convert to an MSI Given the npukg and manifest from workload owner, a tool can convert to an msi #14952
• Acquisition of optional workloads in VSfM VS mac update/installer - .NET SDK integration #16484
• When a workload is missing, trigger the IDE acquisition experience When a workload is missing, trigger the product acquisition experience #14953
• Acquisition of the workloads
  • Non-admin install of the workload SDK managed workload installer #16483
  • Update Workload manifest Workload manifest updates #16891
  • Uninstall and update for the workloads Uninstalling and updating an optional workload #14955
  • Repair workloads installation Repair workloads installation #16783
  • Workload restore #17432
  • Admin install Admin install for optional workloads #14956
  • NuGet package download API Improve NuGet package download API #16470
  • data/UnixFilePermissions.xml Given data/UnixFilePermissions.xml in pack nupkg, when extract package, nuget package extractor can set executable permission according to the file #16894
  • surface manifest description surface manifest description #17095
  • advertise manifest "back ground" update check Advertise manifest "back ground" update check #17394
    • Add documentation for environment variables that control this
    • Add message notifying of available workload updates #18994
  • workload list (show what is installed) workload list (show what is installed) #17392
  • workload search(show what is available to install) workload search(show what is available to install) #17393
  • Add support for critical workload updates (more visibility? block build? needs design) Add support for critical workload updates (more visibility? block build? needs design) #17395
  • Add a block to prevent multiple workload install, uninstall, repair, restore, or upgrade steps from happening at the same time #18992
  • Clean up <DOTNET ROOT>/metadata/temp/ in case process crashed #18993
  • Display message in first run experience if workloads from previous install need to be updated #19060
  • Should the SDK resolver look at the workload installation record before resolving a workload pack? This would mean the workloads that are available to an SDK would match the user intent (recorded as the installation record) of what should be installed. Otherwise workload functionality may light up because a different SDK installed the same workload packs, or because we couldn't actually garbage collect workload packs that were uninstalled in a lower SDK version.
  • Update command-line error behavior in workload resolver spec to check whether workloads were never installed, or whether they were installed but need to be updated. Adjust error message appropriately. Possibly we can just adjust the message to tell users to either run "install" or "update"
• workload manifest insertion authoring workload manifest insertion authoring #17020
• error message and user experience when the user are not elevated error message and user experience when the user are not elevated  #17087

[marcpopMSFT]

FYI to @wli3 as we closed out the optional workload issues for .net 6. Thanks for the hard work!