Test case for analyzer dependency loading #75487
Merged
Conversation
This file contains 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
Teams were asking about whether or not the compiler will handle multiple analyzers taking a dependency on the same utility DLL at different versions (when it's strong named). This adds a test that goes through that scenario to validate it will work.
dotnet-issue-labeler
bot
added
Area-Compilers
untriaged
|
@RikkiGibson, @dotnet/roslyn-compiler PTAL |
RikkiGibson
approved these changes
Oct 14, 2024
| sb.AppendLine(""Delta.2: "" + s); | ||
| } | ||
|
|
||
| public void M2() |
There was a problem hiding this comment.
It looks like the only real change in here is that 'M1' and 'M2' were added, right?
This was referenced Oct 22, 2024
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.
Teams were asking about whether or not the compiler will handle multiple analyzers taking a dependency on the same utility DLL at different versions (when it's strong named). This adds a test that goes through that scenario to validate it will work.