Hi Greg, I know, it is a minefield. Have you considered perhaps creating you own message class. Using MessageContracts ( http://msdn.microsoft.com/en-us/library/ms730255.aspx) gives you full control over the contents of your SOAP message including the header. There is of course some additional overhead in doing this but might be what you are looking for.
Stephen On 12 June 2010 22:49, Greg Keogh <g...@mira.net> wrote: > Well, I’ve printed off and read 2 of the blog articles on WCF, behaviors, > headers and message inspectors. Then I read them again, and again and again. > Every single line of code that touches WCF is like an impenetrable and cruel > puzzle to torture your mind. There are so many seemingly uncorrelated > classes, methods, bases, properties and methods that it’s like someone threw > them all into a bag and drew them out like a lottery draw. > > > > I can understand that the authors of WCF had a challenging task, and to > create the general purpose extensible product they had to invent the long > and complex pipeline that makes it work. But it’s like they couldn’t have > made it harder to use and understand if they tried. James Joyce wrote > Finnegans Wake to confound and frustrate us, and someone wrote WCF for the > same purpose. > > > > I remember it took me an hour at most to get my first ws SOAP header > working from scratch several years ago. I reckon it could take me a whole 8 > hour day to get the same functionality working in WCF. Oh well, what better > things are there to do on a Sunday? > > > > Greg >
