Hi all. For documentation purposes one of the things I've done is write up a single sample that implements **almost** all of the ServiceModel extension interfaces in the December CTP and I'll post it here. But first, I'll summarize the extension system...

Because there have been a few changes along the path of the product, I thought I'd make it clear how OperationContext works with respect to adding and reading out-of-band headers in the messages using headers that do not appear in the service contract...

Here's something that I didn't expect. Do people have the same result I do? After the preceding post, I expected this to run correctly, and it doesn't. ChannelFactory<ISampleService> factory = new ChannelFactory<ISampleService>(); foreach...

The following code fixes the earlier code that I leave posted just to confuse people. (Actually, so that you can see the difference between them.) Here I use a new factory or ClientBase proxy each time I change the endpoint the client will invoke. The...

Bummer? Sorta, but not really. To the quick: Once the channel has been created for a proxy, any subsequent invocations on that proxy use the original channel. This is true even if, as I did in this sample here ( http://blogs.msdn.com/ralph.squillace...