Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m developing a .net WPF application, and I would like to put in a two way IPC mechanism. I realize named pipes and remoting are options, however I would like to make the mechanism not dependent on .NET for non-.NET applications to communicate with my application.
What does SO recommend as a solution to this? WM_COPYDATA?
I would use named pipes, in this case.
Named pipes are fully supported in native code as well as .NET. They provide a very fast, efficient way of working, and are very easy to work with in .NET for your current development. This is a much better option (in just about every way, IMO) to WM_COPYDATA.
That being said, there are quite a few Interprocess Communication options. Many of these work both in .NET and native code, including: