There was a typo in DependsOnTargets attribute of the
_AddCorlibReference target definition. It didn't break any
behaviour, since the target it depended on was always built
earlier in the build anyway, so it was really a sanity check.
However, it broke the tests for the new (unused) engine,
Microsoft.Build.dll, which checks for unexpected attributes.
<DocFileItem Include="$(DocumentationFile)" Condition="'$(DocumentationFile)' != ''"/>
</ItemGroup>
- <Target Name="_AddCorlibReference" DependsOn="GetReferenceAssemblyPaths">
+ <Target Name="_AddCorlibReference" DependsOnTargets="GetReferenceAssemblyPaths">
<!--
HACK: We don't yet support property functions, so can't calculate FrameworkPathOverride
by calling ToolLocationHelper.GetPathToStandardLibraries. Instead, we search the framework
<DocFileItem Include="$(DocumentationFile)" Condition="'$(DocumentationFile)' != ''"/>
</ItemGroup>
- <Target Name="_AddCorlibReference" DependsOn="GetReferenceAssemblyPaths">
+ <Target Name="_AddCorlibReference" DependsOnTargets="GetReferenceAssemblyPaths">
<!--
HACK: We don't yet support property functions, so can't calculate FrameworkPathOverride
by calling ToolLocationHelper.GetPathToStandardLibraries. Instead, we search the framework