If you want your Web Service to use the WS-I Basic Interop Profile based on SOAP 1.1, then that's an easy job with Windows Communication Foundation (WCF) using the BasicHttpBinding pre-defined binding.
Similarly, if you want your Web Service to use the full Advanced Web Services Profile based on SOAP 1.2 and WS-Addressing, then that's also an easy job with WCF using one of the other pre-defined bindings such as WsHttpBinding or WsFederationHttpBinding.
However, if you want your Web Service instance to use a less common configuration such as SOAP 1.1 + WS-Addressing, then you need to do a little more work yourself. Just add a WCF "custom binding" to your App.config file that specifies the combination of transport, SOAP and WS-Addressing versions to use. Here's an example of how that might look:
<customBinding>
<binding name="Soap11AddressingBinding" >
<textMessageEncoding messageVersion="Soap11WSAddressing10" />
<httpTransport/>
</binding>
</customBinding>
Copyright © 2002-2008 Jorgen Thelin.
All rights reserved.
This weblog is licensed under a
Creative Commons License.