-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Have ProjectInSolution.AbsolutePath return a normalized path #5950
Merged
rainersigwald
merged 2 commits into
dotnet:master
from
jeffkl:fix-projectinsolution-absolutepath
Dec 16, 2020
Merged
Have ProjectInSolution.AbsolutePath return a normalized path #5950
rainersigwald
merged 2 commits into
dotnet:master
from
jeffkl:fix-projectinsolution-absolutepath
Dec 16, 2020
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
jeffkl
force-pushed
the
fix-projectinsolution-absolutepath
branch
from
December 10, 2020 16:48
46ffea4
to
74b8fc6
Compare
jeffkl
changed the title
WIP
Have ProjectInSolution.AbsolutePath return a normalized path
Dec 10, 2020
jeffkl
force-pushed
the
fix-projectinsolution-absolutepath
branch
from
December 11, 2020 18:17
85d8ddb
to
b4d19f6
Compare
Forgind
reviewed
Dec 14, 2020
jeffkl
force-pushed
the
fix-projectinsolution-absolutepath
branch
from
December 14, 2020 20:03
b4d19f6
to
3eed692
Compare
Forgind
approved these changes
Dec 14, 2020
rainersigwald
approved these changes
Dec 15, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally I'd like it interactive rebased to have a commit for the shouldly migration and a separate commit for the actual change.
jeffkl
force-pushed
the
fix-projectinsolution-absolutepath
branch
from
December 15, 2020 16:50
c1dbf39
to
fc8e5cf
Compare
jeffkl
added a commit
to jeffkl/msbuild
that referenced
this pull request
Mar 10, 2021
dotnet#5950 introduced a call to `Path.GetFullPath()` to get a path that is normalized. However, in some cases Visual Studio stores unsupported paths which will cause `Path.GetFullPath()` to throw. `Path.GetFullPath()` can also throw a `PathTooLongException` which is now handled. Fixes dotnet#6236
benvillalobos
pushed a commit
to benvillalobos/msbuild
that referenced
this pull request
Mar 16, 2021
dotnet#5950 introduced a call to `Path.GetFullPath()` to get a path that is normalized. However, in some cases Visual Studio stores unsupported paths which will cause `Path.GetFullPath()` to throw. `Path.GetFullPath()` can also throw a `PathTooLongException` which is now handled. Fixes dotnet#6236
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 change updates
ProjectInSolution.AbsolutePath
to return a normalized path. At the moment it simply returns the result of aPath.Combine()
which leaves..\
path segments in place and does not contain OS-specific path separators.Fixes #5949 and NuGet/Home#10307