What should I know when developing a compatible WCF web service?

I am starting this Wiki to collect best practices for creating compatible web services (not clients) in WCF. Share your experience if you know a feature that is usually not compatible or not compatible with a particular platform.

+5
source share
3 answers

Pretty simple:

  • avoid any .NET features such as Exceptions (turn them into SOAP errors)

  • , net, netTcp, netNamedPipes, netMsmq .. - wsHttpBinding WS- * - basicHttpBinding /

  • NetDataContractSerializer

+4

WCF REST, , xml .

+3

:

  • HTTP HTTPS
  • (negotiateServiceCredential ). TLSNego SPNego, .
  • HTTP .
  • Binary HTTP encoding is not compatible
  • OleTransactions do not interact.
  • Use service security context with caution (EstabilishSecurityContext in message security). It uses the WS-Secure Conversation protocol, which is not available on some platforms.

Edit:

  • WSDualHttpBinding and CompositeDuplexBindingElement do not interact.
+3
source

All Articles