Yesterday I had to build a custom message encoder to be able to call a legacy POX service with iso-8859-1 encoding. It turned out that the service had another surprise to me: it needs an HTTP user-agent header. It's something quite simple to accomplish with WCF . All it's needed is to add the...
I'm a newbie in WFC and, so far, only have done client code to call POX web services. I've been using a textMessageEncoding binding extension with a message version of None and a write encoding of utf-8 and all has been running fine. Well, until I needed to call a service in iso-8859-1 encoding...
There's an interesting discussion going on on the Architecture General MSDN Forum . Check it out.