开发可互操作的WCF Web服务时我应该知道些什么? [英] What should I know when developing interoperable WCF web service?

问题描述

我正在启动此Wiki，以收集有关在WCF中创建可互操作的Web服务(而非客户端)的最佳实践.如果您知道通常无法互操作或不能与特定平台互操作的任何功能，请分享您的经验.

I'm starting this Wiki to collect best practices about creating interoperable web services (not clients) in WCF. Please share your experience if you know any feature which is not generally interoperable or which is not interoperable with specific platform.

推荐答案

非常简单:

• 避免使用任何类似NET的异常(将异常转换为SOAP错误)

• avoid any .NET specifics like Exceptions (turn them into SOAP faults)

请勿使用以net开头的任何绑定，例如netTcp，netNamedPipes，netMsmq等-使用wsHttpBinding以获得安全的WS- *服务，使用basicHttpBinding以获得最大的覆盖范围/与偶数的兼容性最奇怪的客户端平台

don't use any binding that start with net like netTcp, netNamedPipes, netMsmq and so forth - use wsHttpBinding for secure WS-* services, and basicHttpBinding for maximum reach / compatibility with even the weirdest client platforms

不要使用NetDataContractSerializer

don't use the NetDataContractSerializer

这篇关于开发可互操作的WCF Web服务时我应该知道些什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！