Wcf Exception Shielding - Unexpected FaultContracts

nospam@example.com (Twan Jacobs) — Fri, 27 Mar 2009 15:21:54 +0000

So you've got Wcf Exception Shielding in place. All is well and the Enterprise Library Exception Handling Application Block takes care of those nasty exception details that you don't want your site visitors to know about... But have you ever had the urge to do more than just property mapping between exceptions and FaultContract? I know I have

There is a way to do this and it is actually quite simple to realize. You just have to create your own custom IExceptionHandler. But let's start with a bit of configuration. By default you would have an Exception Policy named "WCF Exception Shielding". Like so:

This policy handles specific Exception types and for each of those it will pass the exception through a chain of IExceptionHandlers. The last of these would normally be Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.WCF.FaultContractExceptionHandler. For instance:

Now what if your FaultContract would need additional data, that you can't just map from the Exception properties? For example:
- you might need the Message property of the InnerException;
- you need data that was logged to a database when the original exception got thrown.

To make this possible, just create your own IExceptionHandler that will be used instead of the provided FaultContractExceptionHandler. There are two things to keep in mind when you do this. First of all you should always set the postHandlingAction to ThrowNewException. Second, you should let your IExceptionHandler return a specific Exception type: FaultContractWrapperException.
Continue reading "Wcf Exception Shielding - Unexpected FaultContracts"

Proxy's Dispose results in Exception

nospam@example.com (Twan Jacobs) — Tue, 27 Jan 2009 09:58:10 +0000

A while ago I grabbed a WCF Membership example from here. Now that I've been reading some more on WCF, I stumbled upon the following article: http://msdn.microsoft.com/en-us/library/aa355056.aspx

How do you see this? Have you ever had these 'errors from IDisposable' surface in production? Did you start rewriting every client call with try-catch-finally? Personally I'm a bit appalled by the idea... Using the using statement keeps the code clean.

So I started searching for a solution. This article (WCF Gotcha #1) seems to provide a nice solution, but it's not exactly what I was hoping for.

Ideas are very welcome!
Continue reading "Proxy's Dispose results in Exception"

Arogl Darthu's Blog - WCF

Wcf Exception Shielding - Unexpected FaultContracts

Proxy's Dispose results in Exception