wcf - Prevent Named Pipes Conflict -

We have a .NET program that uses WCF to communicate with another process. We have used designated pipes. Service Host Host = New Service Host (Typef (Something), New URI [] (New Uriyi ("netpopi: // localhost")}); Host.AddServiceEndpoint (typeof (ISomething), New NetNamedPipeBinding (), "Something"); host.Open ();

Code worked great till third party .NET program was installed. Now open "not on pipe name Can be heard with the message "net.pipe: // localhost / ', because another pipe endpoint is already listening on that name."

My impression is that the other Program is already using named pipes Is there a workaround or is there a programmable pipe designated on the computer program? I get other questions that you can set a "name" for the pipe, so it You can not fight with other procedures, how do you do it?

Can use the programming dub Take a look at Juwel Lovie's Service ModelX from your book of LCF Services. You will see how he prepares the name of the pipe, he uses the code that looks like this:

  Uri bassadder = new Uri ("net.pipe: // localhost / "+ Guid.NewGuid () ToString ());  

Name conflicts should be avoided.