Rainer Sigwald

Hm, that's an unfortunate result of some of our design decisions. Maybe if we're in tl auto-mode and there are clp arguments we should go back to console logger?

> When does 17.12 go out of support? We don't know yet, unfortunately.

> If fixes are required after the .NET SDK is out of support, the solution would be to move your branch forward onto a newer .NET SDK (.NET 10 probably),...

A bunch of our tests overlay the just-built MSBuild onto some known-good SDK and use that to build stuff--historically that's been "the one we used to build ourselves" requiring TF...

That's the version of the .NET runtime that's packaged into 9.0.200 builds right now: https://github.com/dotnet/sdk/blob/10e47c896095ad44c053e99d4e4664bd02984bab/eng/Version.Details.xml#L18 @marcpopMSFT, is there an easy way to flow the rc2 runtime to SDK release/9.0.200 so...

We have made many changes to remove LINQ from hot paths over the years, and I think we should continue down that path: if something is causing a problem and...

I'd love to see evidence in the form of profiles or other quantitative measures of impact here. Without that this feels likely to introduce bugs without noticeable impact.

> @dotnet/kitten how worried should I be that I couldn't build this with minimum msbuild being 17.11.0 or 17.11.3. I'm trying 17.11.4 as that appears to be what it's finding...

@marcpopMSFT we may actually want to restrict the MSBuild version to 17.11.9, which has the STJ bump fix that fixed 9.0.100-rc.1. We could publish those packages if you need them.

> Looks like the resolver uses an unstable build number rather than the stable version. Did that change at some point as I don't think we had this sort of...