Rainer Sigwald

IIRC we've also seen some timing things, maybe it's setting NoWarn after it's already been read into MSBuildWarningsAsMessages?

We actually use xUnit v2 today. I am not opposed to moving and prefer to dogfood .NET projects, but we're not currently hitting a huge amount of friction with our...

_Yield_ doesn't save environment/cwd, but the MSBuild engine will do so before switching the node to another project context, and we may decide to do so at any time after...

IMO actual-now makes sense to me--determinism is IMO important for the _images_ and not so much for the manifests. I created precedent for that in #89. SDK version (or "file...

Migrating this here because MSBuild and the Sdk do the right thing--a command line build of the app builds only the `net45` version of the lib in this example. Visual...

I just had a horrible/interesting thought about this. On very-high-core-count systems (like 64+), Windows and .NET often don't scale to having threads for all of the cores (see all our...

We log that error, but it doesn't get a project context assigned. That's why it's in a separate section in the console output. This seems reasonable since we'll only attempt...

I signed off on the PR--current main (this is a recent PR build, arm64 linux) runs CoreCompile in that project multiple times but this one does it once

Is it possible to infer this? Aren't there Windows-based containers with the same multi-arch image name, for example `mcr.microsoft.com/dotnet/runtime:6.0` is an alias for both Debian `6.0.8-bullseye-slim-amd64` and Windows Sever Core...

Right now we just [`Path.Combine` the relative path with the solution file directory](https://github.com/Microsoft/msbuild/blob/7a255b89c90c38520b5cc6869a5e2a2f1e66da20/src/Build/Construction/Solution/ProjectInSolution.cs#L167). Perhaps we should normalize `_relativePath` [in its setter](https://github.com/Microsoft/msbuild/blob/7a255b89c90c38520b5cc6869a5e2a2f1e66da20/src/Build/Construction/Solution/ProjectInSolution.cs#L157)?