I'm attempting to set up a low-level keyboard hook using P/Invoke in an F# application. The Win32 function SetWindowsHookEx
takes a HOOKPROC
for its second argument, which I've represented as a delegate of (int * IntPtr * IntPtr) -> IntPtr
, similar to how this would be handled in C#. When calling the method, I get a MarshalDirectiveException
stating that the delegate parameter cannot be marshaled because
Generic types cannot be marshaled
I'm not sure how generics are involved, as all types are concretely specified. Can anyone shed some light on this? Code follows.
EDIT
This may have to do with the way the F# compiler deals with type signatures - Reflector indicates that the delegate LowLevelKeyboardProc
is implemented as a method which accepts one argument of type Tuple<int, IntPtr, IntPtr>
- and there would be the un-marshalable generic type. Is there a way around this somehow, or are F# functions simply not capable of being marshaled to native function pointers?
let WH_KEYBOARD_LL = 13
type LowLevelKeyboardProc = delegate of (int * IntPtr * IntPtr) -> IntPtr
[<DllImport("user32.dll")>]
extern IntPtr SetWindowsHookEx(int idhook, LowLevelKeyboardProc proc, IntPtr hMod, UInt32 threadId)
[<DllImport("kernel32.dll")>]
extern IntPtr GetModuleHandle(string lpModuleName)
let SetHook (proc: LowLevelKeyboardProc) =
use curProc = Process.GetCurrentProcess ()
use curMod = curProc.MainModule
SetWindowsHookEx(WH_KEYBOARD_LL, proc, GetModuleHandle(curMod.ModuleName), 0u)
Have you tried to use managed C++ with this. It can make a lot of the translation pretty seamless. You won't need P/Invoke then.
EDIT: I'd like to note one fairly important thing: compiler will do more type-checking for you. I am sure you love your type-checking, since you use F# for the rest of the app (hopefully).
Your
LowLevelKeyboardProc
definition is wrong. Change fromto
or better yet
or better yet
In all of the above cases,
proc
will need to use curried form rather than tupled form.Also note that you should add
SetLastError = true
to all of theextern
ed functions whose documentation says to callGetLastError
upon failure (which is the case forGetModuleHandle
,SetWindowsHookEx
, andUnhookWindowsHookEx
). That way if any fail (and you should be checking the return values...), you can simply raise aWin32Exception
or callMarshal.GetLastWin32Error
to get proper diagnostics.EDIT: Just for the sake of clarity, here are all the P/Invoke signatures I successfully tested locally:
Also note that this would work equally as well, if you prefer value semantics for
KBDLLHOOKSTRUCT
: