I have to consume to a third-party web service using SOAP. It was easy to get it to work with WCF, but now I have a problem with SOAP faults. The service sends me an incorrect S
I believe the old-school System.Web.Services.SoapHttpClientProtocol class is more tolerant of not-up-to-snuff-or-standard Faults than the WCF System.ServiceModel.Channels.ServiceChannel.HandleReply / System.ServiceModel.Channels.MessageFualt.CreateFault.