For those who can't (or don't want to) deploy .NET Framework 3.5, the service packs included for the 2.0 and 3.0 versions of the framework are available as standalone downloads. Microsoft .NET Framework 2.0 Service Pack 1 (x86) Microsoft .NET Framework 2.0 Service Pack 1 (x64) Microsoft .NET...
Posted to
Paulo Morgado
(Weblog)
by
Paulo Morgado
on
11-22-2007
Filed under: .NET, WinForms, ASP.NET, SoftDev, C#, Microsoft, MSDN, MVP, VisualStudio, WCF, WPF, WF, WindowsClient
Continuing the improvement of the CustomTextMessageEncoder (see this and this ), this time I'll use the XmlDictionaryWriter instead of the XmlTextWriter whenever the character encoding is utf-8 , utf-16 or Unicode . To achieve this, all that's needed is to look into the character set part of...
As I told before I've been using WFC to call legacy POX web services. Some of them only accept iso-8859-1 , others can accept utf-8 , but all use MessageVersion.None and the text/xml media type. But since the new XmlDictionaryWriter is optimized for utf-8 , utf-16 and Unicode character encodings...
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.
Pedro Félix is blogging about WCF .