I've been having a lot of fun recently thinking about how clients can fail to connect to one endpoint and recover to find any other endpoint for that contract that a service supports. The MetadataResolver class makes it real easy, at least, I think so...

There's nothing fancy about what WCF does to release callbacks on the UI thread -- it just picks up the SynchronizationContext and away it goes. However, to pick that context up properly, you must make sure to initiate the system after Application.Run...

I have just fixed a bug in the docs in which the xml namespace is left out of the topic for WSDL.exe when using the /parameters switch. The <wsdlParameters> element must have the namespace, so it must be: <wsdlParameters xmlns=" http:/...