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
about WCF behaviours was wasted, as many
WCF interfaces are not supported on the Silverlight client. I stumbled over
an article that pointed I have to do the following (simplified real code).
The code is a bit obtuse because I had to use Action callback combined
with using to keep
Folks, I'm revisiting a topic I raised about a year ago on how to simulate
SOAP Headers in WCF. Back then I had a problem where dozens of methods in my
WCF service all needed the same argument passed in every call, and it was
crazy to manually add the argument to dozens of methods. In the Web
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
