Hooking mit WinAPI über C#

Quote:

Originally Posted by MSDN Key strokes are converted into characters by the TranslateMessage function, which we first saw in Module 1. This function examines key-down messages and translates them into characters. For each character that is produced, the TranslateMessage function puts a WM_CHAR or WM_SYSCHAR message on the message queue of the window. The wParam parameter of the message contains the UTF-16 character.

using (Process curProcess = Process.GetCurrentProcess())
            using (ProcessModule curModule = curProcess.MainModule)
            {
                // curModule.ModuleName: Diablo III.exe
                _hHook = SetWindowsHookEx(WH_GETMESSAGE, proc, GetModuleHandle(curModule.ModuleName), 0);
            }

Quote:

ERROR_HOOK_NEEDS_HMOD 1428 (0x594) Cannot set nonlocal hook without a module handle.

Quote:

Originally Posted by MSDN WH_KEYBOARD_LL Global only WH_GETMESSAGE Thread or global

Quote:

Originally Posted by MSDN The global hooks are a shared resource, and installing one affects all applications in the same desktop as the calling thread. All global hook functions must be in libraries. Global hooks should be restricted to special-purpose applications or to use as a development aid during application debugging. Libraries that no longer need a hook should remove its hook procedure.

Quote:

Global hooks are not supported in the .NET Framework Except for the WH_KEYBOARD_LL low-level hook and the WH_MOUSE_LL low-level hook, you cannot implement global hooks in the Microsoft .NET Framework. To install a global hook, a hook must have a native DLL export to inject itself in another process that requires a valid, consistent function to call into. This behavior requires a DLL export. The .NET Framework does not support DLL exports. Managed code has no concept of a consistent value for a function pointer because these function pointers are proxies that are built dynamically. Low-level hook procedures are called on the thread that installed the hook. Low-level hooks do not require that the hook procedure be implemented in a DLL.

Quote:

Originally Posted by Dr. Coxxy [Only registered and activated users can see links. Click Here To Register...]

Quote:

Originally Posted by Dr. Coxxy btw. - mit c# noch nie was in der richtung gemacht - aber versteh ich richtig, dass du eh schon mit ner dll im zielprozess rumgurkst? - falls ja, solltest du auch einfach z.b. GetMessage direkt hooken können.

• AttachThreadInput
• ToAscii
• MapVirtualKey
• GetKeyboardState

private IntPtr HookCallback(
            int nCode, IntPtr wParam, IntPtr lParam)
        {

            byte[] ks = new byte[256];

            IntPtr currentHWnd = GetForegroundWindow();
            uint currentProcessID;
            uint currentWindowThreadID = GetWindowThreadProcessId(currentHWnd, out currentProcessID);

            uint thisProgramThreadId = GetCurrentThreadId();

            AttachThreadInput(thisProgramThreadId, currentWindowThreadID, true);


            OnCharEntered("KS:" + GetKeyboardState(ks));
            var vkey = (uint)Marshal.ReadInt32(lParam);
            byte[] ch = new byte[256];
            AttachThreadInput(thisProgramThreadId, currentWindowThreadID, false);


            
            ToAscii(vkey, MapVirtualKey(vkey, MAPVK_VK_TO_VSC), ks, ch, 0);


            OnCharEntered("nCode: " + nCode + " wParam: " + wParam + " lParam: " + lParam + " Map: " + System.Text.Encoding.Default.GetString(ch));
            OnCharEntered("Shift:" + (ks[(int) VirtualKeyStates.VK_SHIFT] & 0x80));

Quote:

Originally Posted by Dr. Coxxy funktioniert da das numpad, € und @ zeichen richtig? ich hab schonmal was in der richtung gemacht, allerdings mit directinput und da mit paar zeichen probleme gehabt.

Quote:

Originally Posted by Master674b Wieso setzt du nicht einfach einen neuen WndProc und rufst dann daraus den originalen WndProc auf wenn du die Nachricht nicht behandelst. Das ist der Standardweg um Input abzufangen. Eine neue WndProc setzt du mit SetWindowLongPtr und GWLP_WNDPROC. Du bekommst dann alle Nachrichten, inklusive WM_CHAR etc.