Forgind

I'm not an expert, but it sounded like they might get the SDK, but we don't have arch-specific packages for them. @baronfel suggested that was an issue you were looking...

> I think that this is not yet accounting for the mapping between user-facing workload set versions and the version of the NuGet package for the workload set. I'll try...

> Note that this will need to be retargeted to release/8.0.3xx now/ I do agree we need to make sure to do this before merging. I've been holding off until...

Windows_NT Build_Release and Darwin Build_Release both failed due to CanBuildProjectWithAPackageReferenceWithMultipleAliases. I didn't bother rerunning them.

Check whether dateTime format is properly outputted for different cultures

> This would close my issue #38681 , since it would allow me to revert to a working state. Providing that it doesn't error out on unsigned packages like every...

Things I tested: 1. Update from rollback still works 2. Workload update records workload set version if applicable 3. Workload set version is loaded and used in populating workload history...

/cc: @joj It sounds like this might be resolved in later versions. Can you triage this when you get the chance?

How is MSBuild intended to find Microsoft.NET.SDK.WorkloadAutoImportPropsLocator? That is, which SDK resolver is supposed to find it, and can you verify whether it's running? I also found this link that...

"uses msbuild to load and evaluate a bunch of csproj files" is definitely a supported use of MSBuildLocator. I suspect that by "build process," YuliiaKovalova was including evaluating a project,...