CODEWITHSUNDEEP
.netipc
Jippers
Jippers

Reputation: 2715

interprocess communication with and without .net

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?

Upvotes: 2

Views: 645

Answers (2)

Reed Copsey
Reed Copsey

Reputation: 564831

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:

  • Clipboard
  • COM
  • File Mapping
  • Pipes
  • Windows Sockets

Upvotes: 2

Steven Sudit
Steven Sudit

Reputation: 19630

Named pipes wouldn't be .NET specific. Neither would shared memory mapping or even TCP/IP. As for .NET remoting, I'd avoid it, even for cases where both sides are .NET.

Upvotes: 0

Related Questions