Reputation: 1312
I'm looking to implement an inter-process messaging solution for a suite of .NET applications that can send a message to every running instance of an app from our toolchain on a single machine. Our messaging requirements were nicely met in the past by using named pipes, and I'm curious as to whether I can adapt our existing infrastructure to send multicast messages. Do .NET pipes support such behavior?
Upvotes: 1
Views: 120
Reputation: 1529
Microsoft Messaging Queue (MSMQ) sound like exactly what you want to do.
Upvotes: 0
Reputation: 754793
.Net can utilize named pipes in the same way native programs can. Check out the System.IO.Pipes
namespace. In particular the NamedPipeClientStream
and NamedPipeServerStream
class. These are just wrappers over the native version of named pipes so it will function in the way you are expecting.
Upvotes: 2
Reputation: 24403
You can use WCF for Multicast Messaging. Here is an example walk through.
Upvotes: 0