Skip to content

UnmanagedFunctionPointer doesn't require field names to be functional #10724

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 1 commit into from
Dec 5, 2024
Merged

UnmanagedFunctionPointer doesn't require field names to be functional #10724

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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/UnmanagedFunctionPointerAttribute.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@
<format type="text/markdown"><![CDATA[
## Remarks
The fields of the <xref:System.Runtime.InteropServices.UnmanagedFunctionPointerAttribute> attribute control various aspects of the transition of a delegate to an unmanaged function pointer, and are the same as the fields with identical names in the <xref:System.Runtime.InteropServices.DllImportAttribute> attribute. These fields are optional, but if you do not specify a field name, <xref:System.Runtime.InteropServices.UnmanagedFunctionPointerAttribute> is ignored.
The fields of the <xref:System.Runtime.InteropServices.UnmanagedFunctionPointerAttribute> attribute control various aspects of the transition of a delegate to an unmanaged function pointer, and are the same as the fields with identical names in the <xref:System.Runtime.InteropServices.DllImportAttribute> attribute. These fields are optional.
For more information about using attributes, see [Attributes](/dotnet/standard/attributes/).
Expand Down
Loading