Inter-Process Communication in .NET Using Named Pipes: Part 1

Ivan L

Rate me:

4.71/5 (92 votes)

14 Jun 20048 min read

490.7K

8.7K

280

This article explores a way of implementing Named Pipes based Inter-Process Communication between .NET applications

dotnetnamedpipes.zip
- AppModule.InterProcessComm
  - AppModule.InterProcessComm.csproj
  - AppModule.InterProcessComm.csproj.user
  - AssemblyInfo.cs
  - bin
    - Release
  - IChannelManager.cs
  - IClientChannel.cs
  - IInterProcessConnection.cs
  - InterProcessConnectionState.cs
  - InterProcessIOException.cs
- AppModule.NamedPipes Reference.chm
- AppModule.NamedPipes
  - APipeConnection.cs
  - AppModule.NamedPipes.csproj
  - AppModule.NamedPipes.csproj.user
  - AssemblyInfo.cs
  - bin
    - Release
  - ClientPipeConnection.cs
  - NamedPipeIOException.cs
  - NamedPipeNative.cs
  - NamedPipeWrapper.cs
  - PipeHandle.cs
  - ServerPipeConnection.cs
- Client
  - App.ico
  - AssemblyInfo.cs
  - bin
    - Release
  - Client.csproj
  - Client.csproj.user
  - Form1.cs
  - Form1.resx
- NamedPipes.sln
- Server
  - App.ico
  - AssemblyInfo.cs
  - bin
    - Release
  - Form1.cs
  - Form1.resx
  - PipeManager.cs
  - Server.csproj
  - Server.csproj.user
  - ServerNamedPipe.cs

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

Written By

Ivan L

Web Developer

United Kingdom

Ivan Latunov is a Software Architect with long term commercial experience in the areas of software architecture and engineering, design and development of web and distributed applications and business and technical analysis. Technical blog. Website: ivanweb.com.

Inter-Process Communication in .NET Using Named Pipes: Part 1

Comments and Discussions