If you need to expose your WCF service to legacy clients as an ASMX web service, use basicHttpBinding

J.D. Meier, Jason Taylor, Prashant Bansode, Carlos Farre, Madhu Sundararajan, Steve Gregersen.

If your service needs to support legacy clients that expect an ASMX web service, consider using the basicHttpBinding. basicHttpBinding does not implement any security by default, if you require message or transport security you should configure it explicitly on this binding. Use basicHttpBinding to expose endpoints that are able to communicate with ASMX-based Web services and clients and other services that conform to the WS-I Basic Profile 1.1. When configuring transport security, basicHttpBinding defaults to no credentials just like a classic ASMX web service

basicHttpBinding has the following characteristics:
  • It does not support ws* stack, therefore it does not provide reliable messaging, message security, and secure transactions.
  • Neither transport or message security is turned on by default.
  • It allows interop with legacy clients which expect to consume an ASMX web service.
  • Allows the service to be hosted in IIS 5 or IIS 6.
  • If you choose to use message security you can only use username or certificates authentication.
  • If you choose to use transport security you can use certificates, Windows or token authentication.

The following example shows a basicHttpBinding configuration section:
<system.serviceModel>
   <bindings>
      <basicHttpBinding>
         <binding name = “myBasicHttpBinding”>
          </binding>
      </basicHttpBinding>
   </bindings>
</system.ServiceModel>

Last edited Apr 17, 2008 at 12:18 AM by prashantbansode, version 1

Comments

No comments yet.