Wednesday 1 December 2010

SOAP header Security was not understood

XML Web services seem to be declining in use, so finding information on this SoapHeaderException proved to be a bit difficult. I added in <soapextensionimportertypes> and installed WSE 3.0, but it made no difference. What worked for me was adding the following line to my code:
webService.SoapVersion =
System.Web.Services.Protocols.SoapProtocolVersion.Soap12;


[Edit 9 Dec 2010]

Actually, this was a red herring. It worked by adding a "service reference", rather than a old-fashioned "web reference".

No comments: