Hi Sharon,
Thanks for your post.
Yes, currently in .Net, there is few build-in support for doing
inter-process communication, we still have to resort to old Win32 ways to
get this done.
In Win32 world, there are a lots of ways to do inter-process communication.
For example, if your applications have UI, we can p/invoke
RegisterWindowMessage to register a system-wide customized message, then 2
applications send/post this message to communicate with each other.(Note:
we can listen this message with overriding Form.WndProc method)
Below is the C++ code to do this, but it should not be hard to convert it
to C# p/invoke code:
http://www.codeguru.com/vb/gen/vb_sy...cle.php/c7401/
Also, we may use WM_COPYDATA message to do the communication. Below is
another C++ article(sorry I can not find any good article on C#):
http://www.codeproject.com/threads/ipc_wmcopy.asp
Further more, if your applications do not have UI, we can not rely on
windows messages. Then we can use other inter-process communication
technologies, such as Named Pipe, Memory Mapped file etc.., please refer to
the articles below:
"Inter-Process Communication in .NET Using Named Pipes, Part 1"
http://www.codeproject.com/csharp/Do...PipesPart1.asp
"A C# Framework for Interprocess Synchronization and Communication"
http://www.codeproject.com/csharp/csthreadmsg.asp
Finally, the .Net way of doing inter-process communication is .Net
Remoting, you can find a lot of articles on .Net Remoting in MSDN or
google.
Hope this helps.
Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.