Rainer Sigwald

Thanks for the repro project, that plus another nice repo from a Microsoft-internal person really helped me understand what's going on here, which is this: 1. Roslyn 4.2 has (transitive)...

Let's leave it open for now to see if it's possible to fix in the MSBuild layer--but right now I don't think it is.

If you use MSBuildWorkspace, it's a transitive reference of that so you can either get a new version with a direct reference to [Microsoft.Build 17.3.1](https://www.nuget.org/packages/Microsoft.Build/17.3.1) or add a direct reference...

> Any idea when this will be investigated? This is important for us! Can you please explain why it's important for you? This is extremely long-standing MSBuild behavior and the...

@AR-May this is related to the request from @olgaark.

@marcpopMSFT don't we have a policy that the analyzers should reference an older Roslyn, congruent with the `minimumMSBuildVersion`?

> This is going to create more problems than it solves. What problems does it create? > remove those from VS MSBuild. This isn't possible, because it would break projects...

I'm personally not tied to the label formats we currently have, but I think it makes sense to preserve a couple of types of label: * **reason**/tenet type labels, like...

The first round of auto-suggestions weren't very good, so I've been trying to label stuff in the hopes that another round of training will help.

Can you please collect a trace of the build by installing [`dotnet-trace`](https://docs.microsoft.com/dotnet/core/diagnostics/dotnet-trace) and running your repro with ``` dotnet trace collect --providers Microsoft-Build -- ./build.sh libs.src ``` ? That should...