Adam Weigert

I have a WCF service available with metadata publishing. I have .NET 2.0 and 1.1 applications that need to use it using the old style Add Web Reference dialog. The reference can be successfully added, but each time I try to call the service I receive a fault, "SOAP header Action was not understood."

What is required to get WCF 3.0 services to work with non-WCF applications



Re: Windows Communication Foundation (Indigo) SOAP header Action was not understood

Brian McNamara - MSFT

Does your WCF service use BasicHttpBinding

Have you checked out this sample http://msdn2.microsoft.com/en-us/library/ms751433.aspx It shows an ASMX client talking to a WCF service.






Re: Windows Communication Foundation (Indigo) SOAP header Action was not understood

Adam Weigert

No, it uses wsHttpBinding ... what do I lose by going to basicHttpBinding

I plan on eventually using an STS to authorize messages, will I not be able to with basicHttpBinding Could I host multiple endpoints in IIS with basicHttpBinding and wsHttpBinding with only a address extension like address="mex" for the MetadataExchange, e.g. address="basic" and the default address is for the wsHttpBinding





Re: Windows Communication Foundation (Indigo) SOAP header Action was not understood

Brian McNamara - MSFT

BasicHttp is interoperable with the old .Net 2.0 & 1.1, whereas WSHttp is not. See

http://msdn2.microsoft.com/en-us/library/ms730017.aspx

(especially the first link there) for some binding comparisons.

You can always host the same service on multiple endpoints, so that one endpoint uses a back-compat binding whereas another endpoint uses a binding with more features. (You can learn more with some of the topics here: http://msdn2.microsoft.com/en-us/library/ms733830.aspx)