DLL communication

[lanman92]

Could someone post some info or a link to communicating with your injected DLL back to the external app through loopback and sockets or something?

[berserk85]

Using Google

Inter-process communication - Wikipedia, the free encyclopedia
CodeProject: Fast IPC Communication Using Shared Memory and InterlockedCompareExchange (updated!). Free source code and programming help
CodeProject: Windows IPC. Free source code and programming help

and so on

[Cypher]

A named pipe would probably be the 'easiest' way. Google that. (Named pipe)

[Shynd]

Named pipes have many positives that, in my opinion, make them the best candidate. Not only are they easy--if you can write to a file handle, you can write to a named pipe, and that includes .NET languages--but if you name the pipe something unique, say, based on the window handle or something--sprintf(szPipeName, ".\\\\pipe\\mypipe_%08X", WoWHWnd);--you can have multiple clients running on one computer, something not generally possible with a Shared DLL.

Sockets are easy in C#, sure, but it's a bit to learn from the C standpoint. Named pipes are as easy as calling CreateFile, ReadFile, and WriteFile from your DLL.

[lanman92]

Thanks for the help. I appreciate it.