如何在 WCF 端点的 XML 配置中指定合约的命名空间？

发布于 2024-10-11 23:44:25 字数 1032 浏览 6 评论 0原文

我有这个 WCF 服务合同（大大简化，但要注意它所在的命名空间）：

namespace Foo.Services.BarService
{
    [ServiceContract]
    interface BarContract {... }
}

在我的 app.config （客户端）中，我为某些服务配置了一个端点：

<endpoint address="..."
          binding="..."
          contract="Foo.Services.BarService.BarContract" />

但是，这个导致错误，指出在支持 BarService.BarContract 的客户端配置中找不到端点。我只能通过将 contract 属性值更改为 BarService.BarContract （即通过删除命名空间）来消除此错误。

这是为什么？这个错误可能来自哪里？为什么我不能提及契约类型的命名空间部分？这是否会导致 WCF 找不到匹配的端点？

回复下面@Ladislav Mrnka评论中的问题：

我说的是客户端。（我忘了提及这一点；对此感到抱歉。）这个错误可能来自服务器端吗？
我通过 Visual Studio 的添加服务引用工具生成了上述服务协定以及实现它的 BarClient 类。我指定了由其他人运行的 BarService 的 URL。我还指定该服务应放置在 Foo.Services.BarService 命名空间中。
打算直接通过为我自动生成的 BarClient 类使用该服务，而不是通过 ChannelFactory。

原文

I've got this WCF service contract (heavily simplified, but pay attention to the namespace it's in):

namespace Foo.Services.BarService
{
    [ServiceContract]
    interface BarContract {... }
}

In my app.config (client side), I configure an endpoint for some service:

<endpoint address="..."
          binding="..."
          contract="Foo.Services.BarService.BarContract" />

However, this results in an error saying that no endpoint was found in the client's configuration that supports BarService.BarContract. I can only get rid of this error by changing the contract attribute value to BarService.BarContract (i.e. by removing the namespace).

Why is that? Where could this error come from? Why must I not mention the namespace part of a contract type? Shouldn't that result even more in WCF not finding a matching endpoint?

Reply to the questions in @Ladislav Mrnka's comment below:

I am talking about the client side. (I forgot to mention this bit; sorry for that.)
Can this error possibly come from the server side?
I generated the above service contract, along with a BarClient class that implements it, via Visual Studio's Add Service Reference facility. I specified the URL of the BarService, which is run by someone else. That's where I also specified that the service should be put in the Foo.Services.BarService namespace.
I was going to use the service directly via the BarClient class auto-generated for me, not via a ChannelFactory<BarContract>.