Hard .Net api type question

[suityou01]

I have a stub driver that received IOCTLS from a C app. I am trying to port this to C#.Net 2008.

The problem is my IOCTLs are getting mangled so the driver doesn't recognise them.
I am using the api declaration from pinvoke.net

 [DllImport("Kernel32.dll", SetLastError = false, CharSet = CharSet.Auto)] public static extern bool DeviceIoControl( Microsoft.Win32.SafeHandles.SafeFileHandle hDevice, Int32 ioctl, [MarshalAs(UnmanagedType.AsAny)] [In] object InBuffer, int nInBufferSize, [MarshalAs(UnmanagedType.AsAny)] [Out] object OutBuffer, int nOutBufferSize, ref uint pBytesReturned, [In] IntPtr lpOverlapped);

and my IOCTL is defined as

 internal static Int32 SIOCTL_TYPE = 4000; 
internal static Int32 METHOD_BUFFERED = 0; 
internal static Int32 FILE_ANY_ACCESS = 0; 
internal static Int32 IOCTL_START_INBOUND_TRAFFIC =((SIOCTL_TYPE) << 16) |((FILE_ANY_ACCESS) << 14) |((0x900) << 2) | (METHOD_BUFFERED);

I know from debugview that the driver receives :

IOCTL code received 262153216

Somehow I think something is wrong with the marshalling, and possible the API call from PInvoke is wrong. On the off chance any of you guys have tried sending IOCTL from .Net can you suggest what is wrong here?

(posted on osronline as well)

[doodab]

internal static Int32 SIOCTL_TYPE = 4000;

might need to be

internal static Int32 SIOCTL_TYPE = 40000;

[eek]

Two (probably totally crap) suggestions

VS2010 is supposedly far friendly when dealing with unruly dll's and com objects on the fly.

Or could you keep the actually (communication) driver within a C++ based wrapper and then call that to retrieve the values.

[VectraMan]

Or could you keep the actually (communication) driver within a C++ based wrapper and then call that to retrieve the values.

WHS. When I had to call a complicated COM interface from C#, I gave up trying to make all the "MarhallAs" stuff work and instead created a C++ .NET wrapper DLL and called that from C#. With C++ .NET you can mix and match .NET and native code within the same function, although the syntax is a bit bizarre. Microsoft call this "IJW" for "It Just Works". Easy to be cynical about something like that from Microsoft, but in this case it just does.