NativePath: use Assembly.CodeBase #1409
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
Use `Assembly.CodeBase` instead of `Assembly.EscapedCodeBase` since the latter does not actually properly escape the path in a reversible way. eg, if a path contains a space, it will be encoded as `%20` in the `EscapedCodeBase` however if a path contains a literal `%20` then it will _also_ be encoded as `%20`.
|
Is there any chance to see this released soon? Edit : Oops didn't see the prerelease package as it's not in the Releases on github https://www.nuget.org/packages/LibGit2Sharp/0.24.0-pre20170124092542 |
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.
Use
Assembly.CodeBaseinstead ofAssembly.EscapedCodeBasesincethe latter does not actually properly escape the path in a reversible
way.
eg, if a path contains a space, it will be encoded as
%20in theEscapedCodeBasehowever if a path contains a literal%20then itwill also be encoded as
%20.Fixes #1389