Tool to find mismatched dependencies #2687
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cquirosj
approved these changes
Nov 10, 2021
tmasternak
approved these changes
Nov 17, 2021
mikeminutillo
force-pushed
the
find-mismatched-dependencies
branch
from
2492841 to
778b0f0
Compare
johnsimons
added a commit
that referenced
this pull request
Nov 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This LINQPad script helps to identify when we have mismatched dependencies.
After a debug build, the script looks for assemblies in the output folders of all projects. For any assembly which appears multiple times, we look for cases where they are different versions and list the projects for them. At the time of creation, the results look like this:
This can be helpful in dealling with Assembly Mismatches