0

I have an application that is moving over from WCF Http to named pipes since everything is on the same machine. Those in charge have decided not to reference the DLLs directly, so that's not an alternative. I'm okay moving over to a tcp connection instead, though I don't know that it gives us any direct performance benefits over http on the same machine. The production host is going to be a IIS 7 server, not a WAS or other service. My machine has IIS 5.1, Cassini, and IIS Express.

I've tried the following:

  • Virtual Box running windows 7 on my XP machine. The installer craps out.
  • Named Pipes on Cassini, not supported.
  • Named Pipes on IIS Express, not supported.
  • Googling the hell out of the solution, nothing useful found.

What is the best/recommended way to develop WCF NetNamedPipes on XP that does not have IIS 7?

4

1 回答 1

2

在 XP 上，WCF 绑定到命名管道非常适合在 Windows 服务进程中自定义托管的服务。但是，如果您不想构建自定义主机，那您就不走运了：在 IIS5/6 中支持的唯一托管协议是 HTTP。

IIS 中为 HTTP 以外的协议托管的 WCF 服务依赖于 WAS，它需要 IIS7。此约束同样适用于 TCP 绑定，因此这不是您建议的解决方法。

听起来好像您的应用程序打算在生产中托管 IIS。如果这是给定的，我认为您别无选择，只能更改为支持目标环境的新开发平台。

于 2012-05-08T17:43:44.637 回答