Interoperability is a mess. From the server side, no matter how long you chip away at it, there always seems to be another client library, or another version of a client library, that will bork.
However, provided your server can talk to it at all, Microsoft's toolchain works really, really well for anybody writing a client. If you are providing a web service and want .NET developers to be interested, you owe it to yourself and them to provide a SOAP interface.
Comments
Interoperability is a mess. From the server side, no matter how long you chip away at it, there always seems to be another client library, or another version of a client library, that will bork.
However, provided your server can talk to it at all, Microsoft's toolchain works really, really well for anybody writing a client. If you are providing a web service and want .NET developers to be interested, you owe it to yourself and them to provide a SOAP interface.