This is to react to the failing tests after the latest MSBuild insertion:
#39093
The test failures have been caused by
dotnet/msbuild#9748
A detailed description of what is going on by @YuliiaKovalova is here:
dotnet/msbuild#9748 (comment)
@sbomer indicates that this is a problem in the way GetValuesCommand is implemented. This is a helper used by various SDK tests, to get the value of a specified property or item group. It does so by injecting a.WriteValuesToFile.g.targets file that defines a target to save the specified property to disk:
|
string injectTargetContents = |
I think there's now a more modern way of getting values from evaluation (-getProperty) as well as an API? Let's investigate converting to that and see if it fixes the tests.
This is to react to the failing tests after the latest MSBuild insertion:
#39093
The test failures have been caused by
dotnet/msbuild#9748
A detailed description of what is going on by @YuliiaKovalova is here:
dotnet/msbuild#9748 (comment)
@sbomer indicates that this is a problem in the way
GetValuesCommandis implemented. This is a helper used by various SDK tests, to get the value of a specified property or item group. It does so by injecting a.WriteValuesToFile.g.targets file that defines a target to save the specified property to disk:sdk/test/Microsoft.NET.TestFramework/Commands/GetValuesCommand.cs
Line 94 in 7d89f5b
I think there's now a more modern way of getting values from evaluation (
-getProperty) as well as an API? Let's investigate converting to that and see if it fixes the tests.