IParameterInspector and Faults
One thing I didn't mention in my past articles about the IParameterInspector in Windows Communication Foundation is how it behaves when an operation returns a fault (throws an exception). The answer is: It doesn't.
When the operation faults, the AfterCall() method in your parameter inspector will never be called.
Technorati: Windows Communication Foundation, WCF, WCF Extensibility
Any idea how to determine if an exception was thrown from within your inspector?
John: I never found a way to do so. I ended up switching to message inspectors as a workaround for my particular need.