在WPF应用程序中托管NamedPipe不会创建管道

Question

I'm on .NET 3.5 I have two WPF projects which should communicate with each other both ways. I figured that named pipes would do the job with WCF making it very easy with duplex mode. However, I start a WCF named pipe host in one application and can't see it in another app. Also

pipelist.exe | findstr "MainApplication"

Where MainApplication is the pipe name returns nothing (pipelist.exe is the utility from SysInternals).

I have the following app.config:

<?xml version="1.0"?>
<configuration>
  <system.serviceModel>
    <services>
      <service name="MainApplication" behaviorConfiguration="Default">
        <endpoint address="" binding="netNamedPipeBinding" name="MainApplication" contract="IMainApplication" />
        <endpoint address="mex" binding="mexNamedPipeBinding" contract="IMetadataExchange" />
        <host>
          <baseAddresses>
            <add baseAddress="net.pipe://localhost/MainApplication" />
          </baseAddresses>
        </host>
      </service>
    </services>
    <behaviors>
      <serviceBehaviors>
        <behavior name="Default">
          <serviceMetadata httpGetEnabled="false" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
  </system.serviceModel>
  <startup>
    <supportedRuntime version="v2.0.50727" />
  </startup>
</configuration>

And the code which should start the listener in Application:

protected override void OnStartup(StartupEventArgs e)
{
    var serviceThread = new Thread(ServiceCommunications);
    serviceThread.Start();

    base.OnStartup(e);
}

private void ServiceCommunications()
{
    var host = new ServiceHost(typeof(MainApplication));

    host.Open();
}

What did I miss? I don't get any exception, however I can't find the pipe when I try to add service reference to my second project, neither I can list it with pipelist.exe Did I miss something basic?

Answer 1

I changed the ServiceCommunications method to

    private void ServiceCommunications()
    {
        var host = new ServiceHost(typeof(MainApplication));

        host.Open();

        while (keepAlive)
        {
            // Do nothing
        }

        host.Close();
    }

And it resolved the issue.