Match project paths case insensitively for windows #1689
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
…project spec MSBuild can return different casings of the file path when evaluting the project at different times. To workaround this all paths should be compared case insensitively on case insensitive file systems. Fixes NuGet/Home#5855
emgarten
requested review from
rohit21agrawal,
PatoBeltran,
nkolev92,
zhili1208,
mishra14 and
jainaashish
jainaashish
approved these changes
Sep 7, 2017
nkolev92
approved these changes
Sep 7, 2017
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.
Match project paths case insensitively for windows
MSBuild can return different casings of the file path when evaluting the project at different times. To workaround this all paths should be compared case insensitively on case insensitive file systems.
Fixes NuGet/Home#5855