WCF wrapping proxy calls to catch errors

[=?Utf-8?B?S2lrZQ==?=]

Hello,

I need to be able to somehow wrap calls made through a standard Interface
used to access a WCF service. The reason for this is to have a higher degree
of control, mainly to catch all kinds of exceptions transperently, and maybe
translate them to other exception types.

I've tried to wrap the interface with a class but that way I can only invoke
methods of the interface passing a string to an execute method
(wrapper.Execut e("MyMethod") ) instead of directly (wrapper.MyMeth od()).
Any way of wrapping proxy calls transparentrly? Any ideas on how to do this?

Many Thanks.

[Spam Catcher]

=?Utf-8?B?S2lrZQ==?= <Ki**@discussio ns.microsoft.co mwrote in
news:98******** *************** ***********@mic rosoft.com:

Hello,

I need to be able to somehow wrap calls made through a standard
Interface used to access a WCF service. The reason for this is to have
a higher degree of control, mainly to catch all kinds of exceptions
transperently, and maybe translate them to other exception types.

I've tried to wrap the interface with a class but that way I can only
invoke methods of the interface passing a string to an execute method
(wrapper.Execut e("MyMethod") ) instead of directly
(wrapper.MyMeth od()).

You can have 2 interfaces, one to implement and one for your service
contract.

The service contract will contain your standard method calls (i.e.
GetUsers, DeleteUser, etc.). The other contract will look something
like:
OnGetUsers.

Then in your service you would call:

Private SomeObject as IMyInternal = New MyInternalImple mentation()

Public Function GetUsers as Users()
Try
IMyInternal.OnG etUsers
Catch Ex as Exception

End Try

Or maybe you can hook into ThreadException and globally catch errors?

--
sp**********@ro gers.com (Do not e-mail)

[Tiago Halm]

If your main objective is to catch errors, and manage the generated fault
exception, then use an IErrorHandler, an implementation of this interface
will be the last bastion before the exception reaches WCF core.

Note: The Microsoft Enterprise Library uses this interface

See more here:
http://msdn2.microsoft.com/en-us/lib...orhandler.aspx

Tiago Halm