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.
相关问题
- How to make a .svc file write to asp.net Trace.axd
- WCF Service Using Client Certificates Requires Ano
- WCF error with net.tcp "The service endpoint faile
- WCF Service Reference Support Files Not Updating
- IntPtr in 32 Bit OS, UInt64 in 64 bit OS
相关文章
- WCF发布Windows服务 POST方式报错 GET方式没有问题 应该怎么解决?
- Using JAX-WS 2.2.5 client with JDK/JRE 1.5
- XCopy or MOVE do not work when a WCF Service runs
- Cannot use org.jvnet.jax-ws-commons.jaxws-maven-pl
- How to create base64Binary data?
- Could not find default endpoint element that refer
- The 'DbProviderFactories' section can only
- Are there any public UDDI registries available?
Fairly simple:
avoid any .NET specifics like Exceptions (turn them into SOAP faults)
don't use any binding that start with
net
like netTcp, netNamedPipes, netMsmq and so forth - usewsHttpBinding
for secure WS-* services, andbasicHttpBinding
for maximum reach / compatibility with even the weirdest client platformsdon't use the NetDataContractSerializer
I recommend WCF REST exposing multiple serialization formats, definitely xml for starters.
General interoperability:
Edit: