Click here to Skip to main content
13,295,616 members (55,455 online)
Click here to Skip to main content
Add your own
alternative version


24 bookmarked
Posted 15 Aug 2006

IPC Between Managed and Unmanaged Code

, 15 Aug 2006
Rate this:
Please Sign up or sign in to vote.
An article about bridging the communication gap between managed and unmanaged code.


Technology keeps leaping forward at a fast pace; applications in projects, large or small, normally cannot keep up with this speed. On one hand, it doesn't make sense to port old code to the new state merely for the status; on the other hand, it also isn't efficient not to use the modern technologies for new designs. Hence, what we get is a mixture of 'old' and 'new' stuff, or as Microsoft depicts it: the Managed and Unmanaged world, creating a new problem when both worlds have to communicate.

There exists, of course, the well-known Inter Process Communication -IPC-, the Microsoft Windows operating system mechanism for facilitating communication and data sharing between applications. This, however, is mainly a property of the old world; the .NET framework does not support such a thing, up till version 2.0. Even then, it is still a question whether it is usable for communication with the old world, or that it is only meant for inter-.NET-communication.

The solution presented here solves this cross-platform problem in a fairly easy and, most of all, simple way, using straightforward methods. Once this path is established, we can also do, for example, .NET Remoting between different machines where one of them is running a legacy MFC application as the object to be communicated with.


Many articles have been written around this IPC topic; the one written by Venkat Raman, called "IPCWorkshop" is quite instructive with respect to the availability of the various communication methods, like MailSlots, NamedPipes, Sockets etc.

Using the code

As said above, the used scheme is very straightforward and easy to understand. The solution consists of two projects: "IPCinCSharp" containing the overridden System.Control.WndProc method, and "SendPostMessageInCSharp" which emulates a VC6-MFC application, firing up the PostMessage event. This emulation is done for simplicity of this article source and demo downloads - it is, of course, possible to use a real VC6 application for this part.


This project does the 'listening to the Operating System messages'; it dispatches the incoming messages identified in the message structure. A threesome switch case is used for the experiment. The WM_MOUSEWHEEL operating system message is handled in this example to know when the user rolled the wheel within the application window area. The WM_APP+number case shows the actual managed-unmanaged base communication stuff: receiving and extracting the WParam and LParam arguments of the Win32-PostMessage function as sent by the "SendPostMessageInCSharp" application.

    MessageBox.Show("WM_MOUSEWHEEL invoked!");

case WM_APP+7232:
    int nWParam = m.WParam.ToInt32();
    int nLParam = m.LParam.ToInt32();
    MessageBox.Show("WM_APP message detected: " + m.Msg +
        "\r\nWParam=" + nWParam + " LParam=" + nLParam);


This part of the code does the emulation of the VC6-MFC application, doing a PostMessage event after finding the target window. Due to the emulation, there are some (irrelevant) part of code in it, like the P/Invoke DllImport, responsible for calling the Win32 API function of PostMessage.

int nHandle = Win32.FindWindow(null,strAppName);
if (nHandle == 0)
    return WindowNotFound;
    int nMsg = Win32.PostMessage(nHandle, 
               nWM_APP, nX, nY); // Fire and Forget ....!
    return AllRight;

The Win32 P/Invoke part:

public class Win32
    public static extern int FindWindow(string lpClassName, 
                                        string lpWindowName);
    public static extern int PostMessage(int hWnd, uint Msg, 
                                         int wParam, int lParam);

The following code snippet can be input into your VC6-MFC application as a button control notification handler code (for the sake of completeness):

HWND hWndTargetWindow;
UINT msg=40000;
UINT wParam=123;
UINT lParam=456;

CString sCaption="SEARCHING Untitled";

if (::FindWindow(NULL, " - Untitled"))
    hWndTargetWindow = ::FindWindow(NULL, " - Untitled");
    PostMsg(hWndTargetWindow, msg, wParam, lParam);
    MessageBox("Untitled Window FOUND!", sCaption, MB_ICONEXCLAMATION);
    MessageBox("ERROR in FindWindow execution!", sCaption, MB_ICONERROR);

That's all there is. Have fun.


  • August 2006 - This is my first CodeProject submission - please be kind.


This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


About the Author

wiet lie
Web Developer
Netherlands Netherlands
No Biography provided

You may also be interested in...


Comments and Discussions

GeneralSpecific approach Pin
Milind Shingade13-Nov-07 1:40
memberMilind Shingade13-Nov-07 1:40 
GeneralRe: Specific approach Pin
wiet lie15-Nov-07 13:26
memberwiet lie15-Nov-07 13:26 
GeneralRe: Specific approach Pin
EricF4-Apr-08 15:42
memberEricF4-Apr-08 15:42 
QuestionCan u Help Me? Pin
Esonix20-Feb-07 0:44
memberEsonix20-Feb-07 0:44 
AnswerRe: Can u Help Me? Pin
wiet lie21-Feb-07 23:02
memberwiet lie21-Feb-07 23:02 
Hi there,

Thank you for the nice response for my article.

Regarding your problem: lots of unclear things to me. Like, are you using this IPC or not; one process is MS-Word, what's the other ... your own code app? Are you trying to modify the textbox containing the "English(US)" string at the status bar, mimicing the Tools>Language>Set Language process?

I do not understand your last line of question: "if i pass code for Bengali(India) then it will be displayed not ENGLISH(U.S) & if i pass Bengali(Bangladesh) then Bengali(Bangladesh) will be displayed.".
Does it mean the following: you instruct your code to display Bengali(India) and the status bar textbox displays "not ENGLISH(US)"?
And then the second half of the line, does it mean that it works correctly, because you instructs to write the string "Bengali(Bangladesh)" and ... indeed "Bengali(Bangladesh)" is printed in the textbox?

So far my uncertainties .... .

Now for what it's worth: if "Bengali(Bangladesh)" works correctly and "Bengali(India)" does not, try looking in the Localization of Windows, maybe Bengali(India) is not in the list.

Good luck!

QuestionHow to use structures for wParam and lParam? Pin
Dieter Geers10-Nov-06 5:57
memberDieter Geers10-Nov-06 5:57 
AnswerRe: How to use structures for wParam and lParam? Pin
wiet lie13-Nov-06 2:13
memberwiet lie13-Nov-06 2:13 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Terms of Use | Mobile
Web02 | 2.8.171207.1 | Last Updated 15 Aug 2006
Article Copyright 2006 by wiet lie
Everything else Copyright © CodeProject, 1999-2017
Layout: fixed | fluid