WCF named pipe minimal example

Question

I m looking for minimal example of WCF Named Pipes  I expect two minimal applications  server and client  which can communicate via a named pipe    Microsoft has the briliant article Getting Started Tutorial that describes WCF via HTTP  and I m looking for something similar about WCF and named pipes   I ve found several posts in the Internet  but they are a little bit  advanced   I need something minimal  only mandatory functionality  so I can add my code and get the application working   How do I replace that to use a named pipe    lt endpoint address  http   localhost 8000 ServiceModelSamples Service CalculatorService      binding  wsHttpBinding  bindingConfiguration  WSHttpBinding ICalculator      contract  ICalculator  name  WSHttpBinding ICalculator  gt       lt identity gt           lt userPrincipalName value  OlegPc Oleg    gt       lt  identity gt   lt  endpoint gt    How do I replace that to use a named pipe      Step 1 of the address configuration procedure  Create a URI to serve as the base address  Uri baseAddress   new Uri  http   localhost 8000 ServiceModelSamples Service        Step 2 of the hosting procedure  Create ServiceHost ServiceHost selfHost   new ServiceHost typeof CalculatorService   baseAddress    try          Step 3 of the hosting procedure  Add a service endpoint      selfHost AddServiceEndpoint          typeof ICalculator           new WSHttpBinding             CalculatorService            Step 4 of the hosting procedure  Enable metadata exchange      ServiceMetadataBehavior smb   new ServiceMetadataBehavior        smb HttpGetEnabled   true      selfHost Description Behaviors Add smb           Step 5 of the hosting procedure  Start  and then stop  the service      selfHost Open        Console WriteLine  The service is ready         Console WriteLine  Press  lt ENTER gt  to terminate service         Console WriteLine        Console ReadLine            Close the ServiceHostBase to shutdown the service      selfHost Close      catch  CommunicationException ce        Console WriteLine  An exception occurred   0    ce Message       selfHost Abort        How do I generate a client to use a named pipe

User · Accepted Answer

I just found this excellent little tutorial  broken link  Cached version   I also followed Microsoft s tutorial which is nice  but I only needed pipes as well   As you can see  you don t need configuration files and all that messy stuff   By the way  he uses both HTTP and pipes  Just remove all code lines related to HTTP  and you ll get a pure pipe example

User · Answer

Try this   Here is the service part    ServiceContract  public interface IService        OperationContract      void  HelloWorld       public class Service   IService       public void HelloWorld                   Hello World           Here is the Proxy  public class ServiceProxy   ClientBase lt IService gt        public ServiceProxy             base new ServiceEndpoint ContractDescription GetContract typeof IService                new NetNamedPipeBinding    new EndpointAddress  net pipe   localhost MyAppNameThatNobodyElseWillUse helloservice                      public void InvokeHelloWorld                 Channel HelloWorld              And here is the service hosting part   var serviceHost   new ServiceHost          typeof Service   new Uri     new Uri  net pipe   localhost MyAppNameThatNobodyElseWillUse           serviceHost AddServiceEndpoint typeof IService   new NetNamedPipeBinding     helloservice        serviceHost Open         Console WriteLine  Service started  Available in following endpoints        foreach  var serviceEndpoint in serviceHost Description Endpoints                Console WriteLine serviceEndpoint ListenUri AbsoluteUri

User · Answer

Check out my highly simplified Echo example   It is designed to use basic HTTP communication  but it can easily be modified to use named pipes by editing the app config files for the client and server  Make the following changes   Edit the server s app config file  removing or commenting out the http baseAddress entry and adding a new baseAddress entry for the named pipe  called net pipe   Also  if you don t intend on using HTTP for a communication protocol  make sure the serviceMetadata and serviceDebug is either commented out or deleted    lt configuration gt       lt system serviceModel gt           lt services gt               lt service name  com aschneider examples wcf services EchoService  gt                   lt host gt                       lt baseAddresses gt                           lt add baseAddress  net pipe   localhost EchoService   gt                       lt  baseAddresses gt                   lt  host gt               lt  service gt           lt  services gt           lt behaviors gt               lt serviceBehaviors gt  lt  serviceBehaviors gt           lt  behaviors gt       lt  system serviceModel gt   lt  configuration gt    Edit the client s app config file so that the basicHttpBinding is either commented out or deleted and a netNamedPipeBinding entry is added   You will also need to change the endpoint entry to use the pipe    lt configuration gt       lt system serviceModel gt           lt bindings gt               lt netNamedPipeBinding gt                   lt binding name  NetNamedPipeBinding IEchoService   gt               lt  netNamedPipeBinding gt           lt  bindings gt           lt client gt               lt endpoint address                 net pipe   localhost EchoService                        binding                 netNamedPipeBinding                        bindingConfiguration    NetNamedPipeBinding IEchoService                        contract                EchoServiceReference IEchoService                        name                    NetNamedPipeBinding IEchoService   gt           lt  client gt       lt  system serviceModel gt   lt  configuration gt    The above example will only run with named pipes  but nothing is stopping you from using multiple protocols to run your service  AFAIK  you should be able to have a server run a service using both named pipes and HTTP  as well as other protocols    Also  the binding in the client s app config file is highly simplified  There are many different parameters you can adjust  aside from just specifying the baseAddress

User · Answer

I created this simple example from different search results on the internet   public static ServiceHost CreateServiceHost Type serviceInterface  Type implementation        Create base address   string baseAddress    net pipe   localhost MyService      ServiceHost serviceHost   new ServiceHost implementation  new Uri baseAddress         Net named pipe   NetNamedPipeBinding binding   new NetNamedPipeBinding   MaxReceivedMessageSize   2147483647      serviceHost AddServiceEndpoint serviceInterface  binding  baseAddress        MEX - Meta data exchange   ServiceMetadataBehavior behavior   new ServiceMetadataBehavior      serviceHost Description Behaviors Add behavior     serviceHost AddServiceEndpoint typeof IMetadataExchange   MetadataExchangeBindings CreateMexNamedPipeBinding    baseAddress     mex        return serviceHost      Using the above URI I can add a reference in my client to the web service

[c#] WCF named pipe minimal example

Examples related to c#

Examples related to wcf

Examples related to named-pipes