Wcf NetNamedPipeBinding在重新启动服务时会产生问题

我们正在使用带有NetNamedPipeBinding的WCF服务。它工作没有任何问题。但当我们在IIS中替换服务的bin或重新启动服务时，客户端将无法与服务连接。在此错误期间，如果我们在客户端将绑定从NetNamedPipeBinding更改为BasicHttpBinding，则可以完美地工作

客户端未收到来自服务的响应。那么，我们如何克服这个问题，只想知道NetNamedPipeBinding的实际问题是什么

如果有更好的NetNamedPipeBinding替代品

更新：

服务端配置

<services>
  <service behaviorConfiguration="ServicesBehavior" name="WcfServices.Service1">
    <endpoint address="soap" behaviorConfiguration="FlattenWsdlEndpointBehavior" binding="basicHttpBinding" contract="WcfServices.IService1">
     <identity>
        <dns value="localhost" />
     </identity>
  </endpoint>
  <endpoint address="json" behaviorConfiguration="webHttpBehavior" binding="webHttpBinding" contract="WcfServices.IService1" />
  <endpoint address="NamedPipe" binding="netNamedPipeBinding" contract="WcfServices.IService1" />
  <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
</service>

<client>
 <endpoint address="http://someAddress/WcfServices/Service1.svc/soap"   binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IService1" contract="WcfServices.IService1" name="BasicHttpBinding_IService1" />
 <endpoint address="net.pipe://localhost/WcfServices/Service1.svc/NamedPipe" binding="netNamedPipeBinding" bindingConfiguration="NetNamedPipeBinding_IService1" contract="WcfServices.IService1" name="NetNamedPipeBinding_IService1" />
</client>

客户端配置

<services>
  <service behaviorConfiguration="ServicesBehavior" name="WcfServices.Service1">
    <endpoint address="soap" behaviorConfiguration="FlattenWsdlEndpointBehavior" binding="basicHttpBinding" contract="WcfServices.IService1">
     <identity>
        <dns value="localhost" />
     </identity>
  </endpoint>
  <endpoint address="json" behaviorConfiguration="webHttpBehavior" binding="webHttpBinding" contract="WcfServices.IService1" />
  <endpoint address="NamedPipe" binding="netNamedPipeBinding" contract="WcfServices.IService1" />
  <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
</service>

<client>
 <endpoint address="http://someAddress/WcfServices/Service1.svc/soap"   binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IService1" contract="WcfServices.IService1" name="BasicHttpBinding_IService1" />
 <endpoint address="net.pipe://localhost/WcfServices/Service1.svc/NamedPipe" binding="netNamedPipeBinding" bindingConfiguration="NetNamedPipeBinding_IService1" contract="WcfServices.IService1" name="NetNamedPipeBinding_IService1" />
</client>

提前谢谢

---

如果有人能在这方面帮助我。

“[是否]有更好的NetNamedPipeBinding替代品”-当然。可以说是下一个最好的局域网，但它没有管道快。请给我们看你的代码，特别是你的配置。@Jacob-这是配置代码