[release/6.0-staging][native-library] If a dllimport is specified with an absolute path, look for it first #85271
Conversation
…ook for it first The unmanaged native library probing documentation says to try absolute paths without variations https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/default-probing#unmanaged-native-library-probing Manual backport of dotnet#85255 to net6
lambdageek
added
Servicing-consider
|
Tagging subscribers to this area: Issue DetailsThe unmanaged native library probing documentation says to try absolute paths without variations Manual backport of #85255 to net6
|
|
Tagging subscribers to this area: Issue DetailsBackport of #85255 to release/7.0-staging /cc @lambdageek Customer ImpactFixes application crashes on MacCatalyst. TestingManual testing RiskLow. This reverts to the behavior before 5a1baeb for DllImports with an absolute path. IMPORTANT: If this backport is for a servicing release, please verify that:
The unmanaged native library probing documentation says to try absolute paths without variations Manual backport of #85255 to net6
|
rbhanda
added
Servicing-approved
ghost
locked as resolved and limited conversation to collaborators
Backport of #85255 to release/7.0-staging
/cc @lambdageek
Customer Impact
Fixes application crashes on MacCatalyst in apps that use system frameworks such as SceneKit.
Testing
Manual testing
Risk
Low. This reverts to the behavior before 5a1baeb for DllImports with an absolute path.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging, notrelease/X.0.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.
The unmanaged native library probing documentation says to try absolute paths without variations
https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/default-probing#unmanaged-native-library-probing
Manual backport of #85255 to net6