[Microsoft.Build] Investigate non-deterministic test behavior

[YuliiaKovalova]

Product

dotnet CLI (dotnet new)

Describe The Bug

When a new item template is instantiated, the warning "Failed to evaluate bind symbol 'langVersion', it will be skipped." is generated sometimes.

Identify what triggers this scenario.
Can be reproduced in the src/Tests/dotnet-new.Tests/DotnetClassTemplateTests.cs tests

To Reproduce

Steps:

1. Go to src/Tests/dotnet-new.Tests/DotnetClassTemplateTests.cs
2. Comment custom scrubber that removes the warning message
3. Run tests a couple of times.

dotnet Info

release/7.2.0xx

[YuliiaKovalova]

Tips for investigation:
Enable debugging logging on the pipeline

[GangWang01]

It was not able to reproduce with release/7.0.2xx after running tests many times locally or in the pipeline.
When we decided to remove scrubbing the warning for further observation in main branch, it is finally reproduced. And I found the warning happened to the following cases of DotnetCSharpClassTemplatesTest which only have shortname. Need to investigate further.

• [InlineData("class")]
• [InlineData("interface")]
• [InlineData("record")]
• [InlineData("struct")]
• [InlineData("enum")]

[GangWang01]

In the item templates mentioned above, the bind symbol langVersion binding to msbuild:LangVersion has different values from the context evaluation of the project without property LangVersion that is done by different versions of the package Microsoft.Build.
For the created library project without language version in the tests, the evaluation result for the bind symbol langVersion in different branches with different versions of the package Microsoft.Build is as below.

Branch	Package Version	Evaluation Result
release/7.0.2xx	Microsoft.Build 17.5.2	11.0
main	Microsoft.Build 17.6.0-preview-23122-03 or above	null

Need to confirm the behaviors of Microsoft.Build are right or wrong.

Here is the direct call from Microsoft.Build https://github.com/dotnet/sdk/blob/6c1b1f5f9e0035df7706467c63b99d264578fab0/src/Cli/dotnet/commands/dotnet-new/MSBuildEvaluation/MSBuildEvaluator.cs#L262 .

[JanKrivanek]

Binlog might be very helpful here to aid investigation.
I'd suggest running the repro with MSBUILDDEBUGENGINE envvar set to 1 (more details: https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Providing-Binary-Logs.md)