Skip to content
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

Add binding redirects for compiler binaries for the LSIF tool #64740

Merged

Conversation

jasonmalinowski
Copy link
Member

Fixes #64491

@jasonmalinowski jasonmalinowski requested a review from a team as a code owner October 14, 2022 18:51
@jasonmalinowski jasonmalinowski self-assigned this Oct 14, 2022
@@ -65,6 +65,9 @@
<PackageReference Include="System.Memory" Version="$(SystemMemoryVersion)" />
</ItemGroup>

<!-- Since we may be loading analyzers in-process, we need to have the appropriate binding redirects in place -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mind sharing a bit more on what this does?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So MSBuild has support for generating binding redirects, and generates them based on what reference it sees that needs it: if you are referencing A.dll and B.dll, and B.dll has a different version of A than you're using, it'll add a reference between those. This is an extra set of targets we have in Roslyn which forces binding redirects from 0 up to the deployed version for all compiler binaries, since we need those to be there for back compat. This is also used for csc, vbc, etc.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooooo I see I see. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants