Include all file paths in analyzer redirecting metadata file #52326
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
This was referenced Jan 6, 2026
This was referenced Jan 6, 2026
Member
Author
|
@333fred @JoeRobich for review; I'd like to get this into 10.0.200 so it's inserted with the SDK into VS; thanks |
JoeRobich
reviewed
Jan 8, 2026
| return false; | ||
| } | ||
|
|
||
| if (!rest.EndsWith("/") && !rest.EndsWith("\\")) |
Member
There was a problem hiding this comment.
Should we be normalizing the paths so that they use consistent separators?
333fred
approved these changes
Jan 8, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Including file paths in the metadata file to avoid needing to discover them at runtime - see dotnet/roslyn#80969 (comment).