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".

1 comment:

Chloe Turner said...

Hey Neil,

I keep stumbling across your profiles on social media, you seem to have some great skills in the MS Stack! Are you enjoying work life at the moment?

If you find yourself looking for new opportunities to challenge your .Net skills I would be keen to help.

I am a recruitment consultant specialising in recruiting in the development space, so please feel free to get in touch if you want to know about other opportunities.

I hope your day is going well?

Kind Regards,

Chloe
Chloe.Turner@Westekrecruitment.co.uk