Thanks Jake, I'll save that code sample. The reason I was so hostile to the
idea of writing behaviours comes from last year where I thought I had to
write one to allow an SL4 app to send authentication data with each WCF
call. I wanted to use the equivalent of a SOAP header which was really easy
to code in the old days to send the extra data out-of-band.
After searching for hours and reading my (awful) SAMS book on WCF I couldn't
even figure out which behaviour was the right one to use, then I'd have to
find a sample because it was really unclear just what arguments and data
were available at what points in the behaviour lifetimes. Then I discovered
that most of the behaviours were unavailable when using SL4 and WCF so was
wasting my time. It turns out I had to have lines like this sample in the
client call:
OperationContext.Current.OutgoingMessageHeaders.Add(MessageHeader.CreateHead
er("id", "ClientService", Ticket.UserId));
I posted the details last year.
Greg
