2.1 Reference resolution project fails to add patched CoreFx assembly to Microsoft.Aspnetcore.App #30279
Labels
area-infrastructure
Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Done
This issue has been fixed
Milestone
In 2.1.26, we found that, despite CoreFx shipping a new version of
System.Text.Encodings.Web
, we failed to include the new version of the binary in Microsoft.Aspnetcore.App``. The reason for this is that the we didn't patch any of the 3 projects that depend on S.T.E.W, so all references to it were resolved asBaselinePackageReferences
, which still point to the unpatched version. I found this by examining the binlog and noticing that, despite `SystemTextEncodingsWebPackageVersion` being updated to 4.5.0, all of the resolved `PackageReferences` to it had version 4.5.0, and were coming from our `ResolveCustomReferences` target. We should fix our logic so that the SharedFx always gets the latest version of any assembly coming from repos below us.Strangely, this behavior was not present for at least one recent ingestion of a patched CoreFx library.
System.IO.Pipelines
was patched in the 2.1.23 build, and we did not ship any patched packages, but Microsoft.AspNetCore.App did include the latest version of System.IO.Pipelines. I haven't figured out why it worked then but not now.Original text from email:
aspnetcore/src/Html/Abstractions/src/Microsoft.AspNetCore.Html.Abstractions.csproj
Line 15 in a401d81
aspnetcore/src/Http/Http.Abstractions/src/Microsoft.AspNetCore.Http.Abstractions.csproj
Line 20 in a401d81
aspnetcore/src/Http/WebUtilities/src/Microsoft.AspNetCore.WebUtilities.csproj
Line 18 in a401d81
aspnetcore/eng/Baseline.Designer.props
Lines 422 to 423 in a401d81
aspnetcore/eng/Baseline.Designer.props
Lines 429 to 431 in a401d81
aspnetcore/eng/Baseline.Designer.props
Lines 1162 to 1164 in a401d81
The text was updated successfully, but these errors were encountered: