Product

dotnet CLI (dotnet new)

Describe The Bug

It seems like there may be some parallel calls to the same workload resolver after it's initialized but before any (serialized) access calls (version or manifests), and it means that we follow the lazy process for computing our manifests multiple times, leading to errors. This should not happen in the first place because the workload resolver should only ever be used from one thread.

One example of this was dotnet/installer#19222

A partial solution is dotnet/sdk#40485, but that doesn't get at the root cause of this instance. We currently believe that root cause is somewhere here.

To Reproduce

See dotnet/installer#19222

dotnet Info

Visual Studio Version

No response

Additional context

No response