-
Notifications
You must be signed in to change notification settings - Fork 292
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
Sync ref project references with runtime projects #2878
Sync ref project references with runtime projects #2878
Conversation
This should enable ResolveAssemblyReferences to generate the correct 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.
This change seems pretty reasonable to me. Let's get the merge conflicts fixed and make sure the test runs pass and we'll get it merged. Thanks for looking into this!
Thanks @benrr101 - just merged! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2878 +/- ##
==========================================
- Coverage 72.31% 72.31% -0.01%
==========================================
Files 288 288
Lines 59660 59660
==========================================
- Hits 43146 43144 -2
- Misses 16514 16516 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@cheenamalhotra can I port this back to the next releases of 5.1 and 5.2? This should let us close #2541 for the remaining supported versions. |
Sure, that makes sense. |
This PR syncs the references of the reference assemblies with those of their respective runtime assemblies. Doing so enables MSBuild's ResolveAssemblyReferences and GenerateBindingRedirects targets to generate the correct binding redirects - so if a downstream library references a later version of Azure.Core or Azure.Identity, VS will generate binding redirects so that SqlClient will use that later version.
Early testing looks promising and I think it'll resolve the issue - but for now, it just relates to #2541 and to #2082.