Inter-process communications
-
hi friends, here is the problem I want to resolve: - I have App 1: a C# application which I'm using now; - I have App 2: a C++ application which exists and can provide me some useful informations I need in my c# application. I want to know how I should do if I want to build a C++ application which will allow communication between application 1 and application 2. Let's call this bridge application, App 3. I want to be able to do following things: 1- send data from App 1 (C#) to App 3 (C++); 2- parse data received from App 1 in App 3; 3- send data from App3 (C++) to App 2 (C++); 4- send back data from App2 (C++) to App 3 (C++); 5- send back data from App 3(C++) to App 1(C#); 6- Display my data in my C# application. Has anyone of you already resolved this kind of "problem". I would like App 3 (C++) to be Systray application which would use windows messages to make interprocess communications. Can you please help me ? I hope I've detailed enough the context. Thanks ! Patrick.
p.f. Goudjo-Ako Bringing our energy together !
-
hi friends, here is the problem I want to resolve: - I have App 1: a C# application which I'm using now; - I have App 2: a C++ application which exists and can provide me some useful informations I need in my c# application. I want to know how I should do if I want to build a C++ application which will allow communication between application 1 and application 2. Let's call this bridge application, App 3. I want to be able to do following things: 1- send data from App 1 (C#) to App 3 (C++); 2- parse data received from App 1 in App 3; 3- send data from App3 (C++) to App 2 (C++); 4- send back data from App2 (C++) to App 3 (C++); 5- send back data from App 3(C++) to App 1(C#); 6- Display my data in my C# application. Has anyone of you already resolved this kind of "problem". I would like App 3 (C++) to be Systray application which would use windows messages to make interprocess communications. Can you please help me ? I hope I've detailed enough the context. Thanks ! Patrick.
p.f. Goudjo-Ako Bringing our energy together !
WM_COPYDATA is the easiest way to communicate between processes. There's no need for a bridging app, in fact, if there was one, then you'd need to handle messages between three apps, instead of two.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
-
WM_COPYDATA is the easiest way to communicate between processes. There's no need for a bridging app, in fact, if there was one, then you'd need to handle messages between three apps, instead of two.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
Hi Christian, thanks for your reply. I'm going to use "WM_COPYDATA" since it seems to the best way to do that. I can't really alter the existing C++ app, but I'll still have a communication by messages sending between two processes because I can create a new c++ app which can use the dependencies from the existing C++ one. I'll have to make communication between my C# application and the C++ one I'll have created. I'm started looking at that. Any idea in using the elements you guys think I'll need is welcome ! Thx ! Pat.
p.f. Goudjo-Ako Bringing our energy together !