Skip to content

Corrected note in DllImportResolver #11865

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Oct 1, 2025
Merged

Corrected note in DllImportResolver #11865

Changes from 5 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
9144b10
Update DllImportResolver.xml
gfoidl Sep 29, 2025
e5c0e2e
Update xml/System.Runtime.InteropServices/DllImportResolver.xml
gfoidl Sep 29, 2025
08db1bc
Update xml/System.Runtime.InteropServices/DllImportResolver.xml
gfoidl Sep 29, 2025
dc8ce6d
Update xml/System.Runtime.InteropServices/DllImportResolver.xml
jkotas Sep 30, 2025
2ef00ab
Update xml/System.Runtime.InteropServices/DllImportResolver.xml
jkotas Sep 30, 2025
009f9a3
Update xml/System.Runtime.InteropServices/DllImportResolver.xml
jkotas Sep 30, 2025
fb8b92b
Update xml/System.Runtime.InteropServices/DllImportResolver.xml
jkotas Sep 30, 2025
8eae963
Update xml/System.Runtime.InteropServices/DllImportResolver.xml
jkotas Sep 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion xml/System.Runtime.InteropServices/DllImportResolver.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@
The runtime does not do any lifetime management around the handle returned by a <xref:System.Runtime.InteropServices.DllImportResolver>. It is left to the implementation and consuming code to keep the library loaded for as long as necessary and free it if/when desired.
The resolver delegate is called everytime when a PInvoke call is done. It is fine to cache the handle, as long as the consuming code does not call <xref:System.Runtime.InteropServices.NativeLibrary.Free>.
For each entry point, the resolver is called the first time PInvoke is used. The implementation of the resolver may want to cache the `libraryName` to handle mapping to improve performance as long as the library isn't unloaded via <xref:System.Runtime.InteropServices.NativeLibrary.Free>, .
]]></format>
</remarks>
Expand Down
Loading