Fix DllImport library names for case-sensitive filesystems #26415
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.
On case-sensitive filesystems (Windows with WSL, developer mode, or per-directory case sensitivity), DllImport fails to load native libraries due to relying on .NET's automatic platform-specific extension/prefix addition, which can produce incorrect casing.
Changes
"onnxruntime"to"onnxruntime.dll"and"ortextensions"to"ortextensions.dll"Impact
Windows: No changes required - libraries already named
onnxruntime.dllLinux/macOS: Native packaging may need updates to provide
onnxruntime.dllin runtime folders (either as actual filename or symlink tolibonnxruntime.so/libonnxruntime.dylib)Fixes #23509
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.