Browse by Tags

All Tags » WCF (RSS)

Pedro Félix Is Blogging

Pedro Félix is blogging about WCF .
Posted by Paulo Morgado | with no comments

.NET Framework 2.0 Service Pack 1 and .NET Framework Service Pack 1 available as a standalone download

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...

Visual Studio 2008 and .NET Framework 3.5 shipped!

Visual Studio 2008 and .NET Framework 3.5 has finally shipped. MSDN subscribers can download the final version of Visual Studio 2008 from MSDN Subscription Downloads , but anyone can get a trial version or an Express Edition . The .NET Framework 3.5 contains...

WCF: Error Code vs Exception?

There's an interesting discussion going on on the Architecture General MSDN Forum . Check it out.

Optimizing reading for the CustomTextMessageEncoder

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...

Optimizing writing for the CustomTextMessageEncoder

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...
Posted by Paulo Morgado | 2 comment(s)
Filed under: , , , , , ,

WCF: Building an HTTP User Agent Message Inspector

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...

WCF: Text Message Encoding and ISO-8859-1 Encoding

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...