Multiple bindings for Soap 1.1 and 1.2 but on the same URI (IIS hosted) RRS feed

  • Question

  • I understand, that in WCF architecture, when we configure the service to have multiple bindings, its required that each bindings be specified with separate and distinct endpoint address.

    I am trying to see, if there is any workaround in WCF to achieve what classic ASMX used to do (same endpoint URI with 2 bindings one for Soap 1.1 and  the other for Soap 1.2)

    Thanks and appreciate your guidance.


    Wednesday, February 10, 2016 1:14 AM


All replies

  • Hello,

    I am afraid there is no way to make a single URI between the two bindings with different SOAP versions in WCF, you would have to config two endpoints for the same service exposed at two different addresses with different bindings.

    The following article is an example on how to do this.



    Wednesday, February 10, 2016 9:15 AM
  • Thanks Jie. Yes thats pretty straightforward and thats how I have implemented it on my side. I was just curious to know if we could some how achieve what classic asmx did.


    Wednesday, February 10, 2016 6:49 PM
  • Hi,

    >> I was just curious to know if we could some how achieve what classic asmx did.

    WCF Service provides all the capabilities of .NET web servies and further extends it. However the ASMX web service is designed to send and receive messages using SOAP over HTTP only. In order to have a better understanding about if we could achieve what classic asmx did, please try to refer to the following articles:
    #The differences Between ASMX and WCF Services: .
    #Choosing Between WCF and ASMX: .

    Best Regards,
    Amy Peng

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, February 22, 2016 2:44 AM