Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[main] Update dependencies from dotnet/runtime #27149
[main] Update dependencies from dotnet/runtime #27149
Changes from 17 commits
50d8a9f
f4b957c
9f9464b
c830a4f
149b6d3
7d38384
d3fc84d
8119940
3ed958e
c237c8e
4ddab3c
37f6666
d9a2f43
c53cffb
954e9bc
c3a59e8
c1b3ba8
92d7d09
2d19ab8
3308817
a3d3230
098e370
eb5ed3b
e552c9b
8cd88bb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was on vacation; what was the specific motivation/break fix for this change?
I think it's ok to go forward with this because we shouldn't care about 17.2 any more, and as long as this moves ahead of MSBuild there should be no problem with adopting a higher version (as long as the task ships both of these assemblies). The
MSBuild.exe
regression tests should catch a problem if there is one.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We were trying to get rid of some old pinned dependencies in dotnet/runtime. The Microsoft.NET.HostModel library was referencing an old version of System.Reflection.Metadata to avoid a break that happened 2 years ago, so we were trying to upgrade it as we felt the break was likely fixed. This particular change is undoing a fix that the SDK repo did to mitigate an issue that came up because the Microsoft.NET.HostModel library was referencing an old version of System.Reflection.Metadata (which as mentioned above, was to avoid an earlier break in the sdk).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then I would recommend deleting the comment entirely; they shouldn't be special any more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the MSBuild binding redirects are actually a little out of date again. They need to be updated for the System.Reflection.Metadata 6.0.1 package (new upper bound assembly version needs to be 6.0.0.1).
In the meantime, (to unblock this PR), I'm going to try to pin this to reference 6.0.0.
To avoid keeping this bad state around, I'll follow up with a PR to MSBuild to update the app.config's binding redirects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've opened a PR to MSBuild with the updated redirect: dotnet/msbuild#7904
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do the MSBuild binding redirects need to match the reference in the task here from SDK? Are the SDK tasks not delivering SRM.dll?