Calling a DLL Function 之一 Passing Structures

Passing Structures

Many unmanaged functions expect you to pass, as a parameter to the function, members of structures (user-defined types in Visual Basic) or members of classes that are defined in managed code. When passing structures or classes to unmanaged code using platform invoke, you must provide additional information to preserve the original layout and alignment. This topic introduces the StructLayoutAttribute attribute, which you use to define formatted types. For managed structures and classes, you can select from several predictable layout behaviors supplied by the LayoutKind enumeration.

Central to the concepts presented in this topic is an important difference between structure and class types. Structures are value types and classes are reference types — classes always provide at least one level of memory indirection (a pointer to a value). This difference is important because unmanaged functions often demand indirection, as shown by the signatures in the first column of the following table. The managed structure and class declarations in the remaining columns show the degree to which you can adjust the level of indirection in your declaration.

Unmanaged signature	Managed declaration: no indirection struct MyStruct(…);	Managed declaration: one level of indirection class MyStruct(…);
DoWork(MyStruct x); Demands zero levels of indirection.	DoWork(ByVal x As MyStruct) Adds zero levels of indirection.	Not possible because there is already one level of indirection.
DoWork(MyStruct* x); Demands one level of indirection.	DoWork(ByRef x As MyStruct) Adds one level of indirection.	DoWork(ByVal x As MyStruct) Adds zero levels of indirection.
DoWork(MyStruct** x); Demands two levels of indirection.	Not possible because ByRef ByRef cannot be used.	DoWork(ByRef x As MyStruct) Adds one level of indirection.

The table describes the following guidelines for platform invoke declarations:

• Use a structure passed by value when the unmanaged function demands no indirection.

• Use either a structure passed by reference or a class passed by value when the unmanaged function demands one level of indirection.

• Use a class passed by reference when the unmanaged function demands two levels of indirection.

 Declaring and Passing Structures

The following example shows how to define the Point and Rect structures in managed code, and pass the types as parameter to the PtInRect function in the User32.dll file. PtInRect has the following unmanaged signature:

BOOL PtInRect(const RECT *lprc, POINT pt);

Notice that you must pass the Rect structure by reference, since the function expects a pointer to a RECT type.

 

C#

using System.Runtime.InteropServices;

[StructLayout(LayoutKind.Sequential)]
public struct Point {
    public int x;
    public int y;
}  

[StructLayout(LayoutKind.Explicit)]
public struct Rect {
    [FieldOffset(0)] public int left;
    [FieldOffset(4)] public int top;
    [FieldOffset(8)] public int right;
    [FieldOffset(12)] public int bottom;
}  

class Win32API {
    [DllImport( "User32.dll")]
    public static extern bool PtInRect(ref Rect r, Point p);
}

 Delcaring and Passing Classes

You can pass members of a class to an unmanaged DLL function, as long as the class has a fixed member layout. The following example demonstrates how to pass members of the MySystemTime class, which are defined in sequential order, to the GetSystemTime in the User32.dll file. GetSystemTime has the following unmanaged signature:

void GetSystemTime(SYSTEMTIME* SystemTime);

Unlike value types, classes always have at least one level of indirection.

    

C#

[StructLayout(LayoutKind.Sequential)]
public class MySystemTime {
    public ushort wYear;
    public ushort wMonth;
    public ushort wDayOfWeek;
    public ushort wDay;
    public ushort wHour;
    public ushort wMinute;
    public ushort wSecond;
    public ushort wMilliseconds;
}
class Win32API {
    [DllImport("Kernel32.dll")]
    public static extern void GetSystemTime(MySystemTime st);
}