Use DllImportSearchPath.AssemblyDirectory for loading jitinterface library #119287
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
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a cross-platform issue with loading the jitinterface library by changing the DLL search path from ApplicationDirectory to AssemblyDirectory. The change ensures proper library loading on non-Windows platforms where ApplicationDirectory is not meaningful.
- Updated the
DllImportSearchPathparameter to useAssemblyDirectoryinstead ofApplicationDirectory
|
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
|
(This is .NET 10 backport candidate.) |
MichalStrehovsky
approved these changes
Sep 3, 2025
|
/backport to release/10.0 |
|
Started backporting to release/10.0: https://github.com/dotnet/runtime/actions/runs/17445055447 |
Merged
4 tasks
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.
DllImportSearchPath.ApplicationDirectorydoesn't mean anything on non-Windows. Switch to usingDllImportSearchPath.AssemblyDirectory, which will search next to the specified assembly or next to the application for single-file applications.See #118999