-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
⬆ Update a bunch of package references #5910
Conversation
9dd7ccc
to
cc31e6b
Compare
I'm not at all opposed to this, but would you mind throwing it in an exp branch (or I can if you'd prefer)? I have a feeling this will cause ngen problems, and if so, it would be good to know what to do before merging. |
VS insertions are blocked on a bunch of upgrades there, but I think dotnet/roslyn#49789 and its linked VS pr will take care of a bunch of that (so thanks, @AArnott!). |
@rainersigwald You are updating some packages that I didn't look at in the VS repo. So if you're taking those dependencies in the devenv.exe process, we may need to update more platform DLLs for this to work. |
branding update
Merge main to 17.0
Merge main into vs17.0
Add the behavior improvements from dotnet#6312 to the 16.10 changewave since they cause failures in cases that didn't fail before.
…tnet#6334) MSBuild redistributes System.Memory but does not binding redirect it. This causes the QB cache plugin to fail (qb.exe works because it has binding redirects, but the plugin fails because it's a dll and dlls don't have binding redirects). Both MSBuild and VS ship with System.Memory 4.0.1.1 so this should not have any negative consequences.
Add explicit reference to Microsoft.DotNet.PlatformAbstractions because it's no longer referenced by Microsoft.Extensions.DependencyModel. Use a version that matches the 2.1 that we use for bootstrapping.
It looks like new CodeDOM doesn't include this any more: dotnet/corefx#35458
28a35b5
to
df2cdc9
Compare
Since it's been almost 7 months, have the platform DLLs AArnott mentioned been updated? If so, other than conflicts, is there anything we need before this can go in? |
No, they haven't. Who knows when we'll get back to this so let's just get rid of it. |
Update a ton of our package references to the latest available version.
I recommend going commit-by-commit on this one.