Skip to content

Commit bc175b4

Browse files
authored
UnmanagedFunctionPointer doesn't require field names to be functional. Fixing the doc to just state that the fields are optional. (dotnet#10724)
1 parent 54c1feb commit bc175b4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

xml/System.Runtime.InteropServices/UnmanagedFunctionPointerAttribute.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@
6161
<format type="text/markdown"><![CDATA[
6262
6363
## Remarks
64-
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.
64+
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.
6565
6666
For more information about using attributes, see [Attributes](/dotnet/standard/attributes/).
6767

0 commit comments

Comments
 (0)