Use BCL APIs to resolve link targets.#14482
Draft
teo-tsirpanis wants to merge 1 commit into
Draft
Conversation
teo-tsirpanis
force-pushed
the
symlink-target-bcl
branch
from
July 22, 2026 01:50
bd4513c to
2993604
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #
Context
#13752 had to resolve paths to symlinks, and did it by P/Invoking to
realpath(3), while there is theFile.ResolveLinkTargetmethod in the BCL. This PR moves to using it.Changes Made
NativeMethods.RealPathand related P/Invoke definitions.File.ResolveLinkTarget.NativeMethods.RealPath. The body of the only method using this API was covered in#if NET.Testing
Notes