WCF 测试客户端显示 IMetadataExchange

发布于 2024-07-12 22:57:52 字数 318 浏览 5 评论 0原文

当我使用 WCF 测试客户端时,它会显示 IMetadataExchange 端点,即使我没有定义端点。 但是,该端点也有一个错误,表明它无法与端点通信。 我已经在一些应用程序上对此进行了测试,并且所有应用程序都会发生这种情况:

“客户端配置中的合同“IMetadataExchange”与服务合同中的名称不匹配。”

有趣的是,这个客户端属于 Visual Studio 2008,我推测客户端 app.config 是由 VS 在后台某处生成的,然后用它来尝试与服务通信。

有任何想法吗? 我正在使用安装了 SP1 的 VSTS Developer。

When I use the WCF Test Client, it shows an IMetadataExchange end point, even if I don't have one defined. However that endpoint also has an error indicating it can't talk to the endpoint. I've tested this on a few applications and it happens with all of them:

'The contract 'IMetadataExchange' in client configuration does not match the name in service contract.'

The funny thing is that this client belongs to Visual Studio 2008, and I presume the client app.config is generated by VS in the background somewhere, then uses it to attempt to talk to the service.

Any ideas? I'm using VSTS Developer with SP1 installed.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

雨巷深深 2024-07-19 22:57:52

试试这个 走过

try this walk through

情深如许 2024-07-19 22:57:52

当您安装了 BizTalk LOB 适配器包时,也会发生这种情况。 不幸的是,就我而言,由于我正在使用这些适配器,因此我无法注释掉演练中所示的部分,因此我必须忍受它(无论如何,WCF 测试客户端对于使用复杂的服务没有用)输入和输出类型)

This also happens when you have the BizTalk LOB adapter pack installed. In my case unfortunately, since I am using those adapters, I can't comment out the section as shown in the walk through so its something I have to live with (in any case the WCF test client is not useful for services that use complex input and output types)

顾铮苏瑾 2024-07-19 22:57:52

Ric 的链接非常接近...我之前在搜索答案时看到过该链接,但忽略了它,因为我没有安装与 Biztalk 相关的任何内容。 事实证明,实际上是 Azure .Net Services SDK 导致了 machine.config 中的恶意条目。 它与一些 Microsoft.ServiceBus dll 相关,我确信这些 dll 是从 Biztalk Services 继承的,因此 Biztalk 链接非常接近。

Ric's link was damn close... I had seen that link earlier in my search for an answer but had disregarded it because I didn't have anything related to Biztalk installed. It turns out it is actually the Azure .Net Services SDK that caused the rogue entry in machine.config. It relates to some Microsoft.ServiceBus dll's that I am sure were inherited from Biztalk Services anyway, so the Biztalk link was very close.

陈年往事 2024-07-19 22:57:52

如果您的计算机上安装了 Windows Azure SDK,请卸载并运行您的测试客户端。它将完美运行

If You Have Installed Windows Azure SDk on your Machine, Please Uninstall,and Run your test Client.It Will Run Perfectlly

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文