Optimizing writing for the CustomTextMessageEncoderhttp://msmvps.com/blogs/paulomorgado/archive/2007/05/06/optimizing-writing-for-the-customtextmessageencoder.aspxAs I told before I&#39;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 forenCommunityServer 2008.5 SP2 (Build: 40407.4157)Optimizing writing for the CustomTextMessageEncoderhttp://msmvps.com/blogs/paulomorgado/archive/2007/05/06/optimizing-writing-for-the-customtextmessageencoder.aspx#893891Mon, 07 May 2007 22:01:46 GMTd67277c4-116b-43f1-b688-e9ef184ea916:893891DotNetKicks.com<p>You've been kicked (a good thing) - Trackback from DotNetKicks.com</p> <img src="http://msmvps.com/aggbug.aspx?PostID=893891" width="1" height="1">Optimizing reading for the CustomTextMessageEncoderhttp://msmvps.com/blogs/paulomorgado/archive/2007/05/06/optimizing-writing-for-the-customtextmessageencoder.aspx#893818Mon, 07 May 2007 20:45:35 GMTd67277c4-116b-43f1-b688-e9ef184ea916:893818Paulo Morgado<p>Continuing the improvement of the CustomTextMessageEncoder (see this and this ), this time I&amp;#39;ll use</p> <img src="http://msmvps.com/aggbug.aspx?PostID=893818" width="1" height="1">