If You Need to Expose Your WCF Service to Legacy Clients as an ASMX Web Service, Use basicHttpBinding

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

If your service needs to support legacy clients that expect an ASMX web service, consider using the basicHttpBinding. The basicHttpBinding does not implement any security by default. If you require message or transport security configure it explicitly using 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, and secure transactions.
  • Neither transport nor message security is turned on by default.
  • 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 basic or certificate authentication.
  • If you choose to use transport security you can use certificates, Windows or Issue token authentication (Windows CardSpace).

The following example shows how to configure basicHttpBinding:
<system.serviceModel>
....
    <services>
        <service behaviorConfiguration="" name="WCFServicecHost.MyService">
            ...
            <endpoint address="" binding="basicHttpBinding" bindingConfiguration=""
                name="basicBinding" contract="WCFServicecHost.IMyService" />
            ...
        </service>
    </services>
</system.serviceModel>

Additional Resources

Last edited Jun 12, 2008 at 9:11 PM by prashantbansode, version 1

Comments

No comments yet.