Wrapping calls to method on a class with a standard try/catch

Question

I have a class that has about 200+ methods, each of these methods makes a call into the database, or a network resource.

Ideally, I would like to wrap each call in a try/catch, to catch any of the common network or SQL exceptions, and give the user the opportunity to try again (if appropriate). However, to add this code to each call would be very time consuming, and bloated as far as the code is concerned.

I've thought about wrapping each of the method calls in another method, creating a delegate, and wrapping the delegate code in the try/catch.. something like this...

(Ignore the syntax.. it's just a conceptual example)

bool CallUpdatePassenger(int PassengerId,string PassengerName,string PhoneNumber) {     Delegate del= Delegate.CreateDelegate(typeof(UpdatePassengerDelegate), typeof(IPassengerServices).GetMethod("RemoteUpdatePassenger"));     bool Res=(bool)CallDelegate(del,PassengerName,PhoneNumber); } object CallDelegate(Delegate del,params object[] args) {     object Result=null;     try     {         Result=del.DynamicInvoke(args);     }     catch (Some.Timeout.Error.Or.Whatever te)     {         // take some action.. maybe retry etc..      }     return Result; } 

Maybe there's a more pracitcal way of doing this ?

The code is automatically generated (by a tool which I wrote) I can quite easily include something like the above, but I want to avoid writing the above code for every method call.

Also, if I do something like the above, I can time methods, and log method calls etc. It just seems a bit clumsy (and not strongly typed).

Thanks Rich.

Answer 1

You should be able to just do something like:

T Execute<T>(Func<T> func) {     try {         return func();     } catch (...) {         ...     } } bool CallUpdatePassenger(some args here) {     return Execute( () => realObj.RemoteUpdatePassenger(some args here)); } 

alternatively, you could use meta-programming to write a dynamic "decorator" for the underlying methods on the fly... but unless you are familiar with ILGenerator etc probably best not to - it is a fairly advanced topic.

Answer 2

I think your basic idea is good, but there's a simpler way to implement it (at least of you're using .Net 3.5 or more recent):

void WithStandardRetryLogic(Action method)  {     try     {         method();     }     catch (Some.Timeout.Error.Or.Whatever te)          {                  // take some action.. maybe retry etc..           }  } 

Example use:

WithStandardRetryLogic(delegate() { CallUpdatePassenger(PassengerId, PassengerName, PhoneNumber); }); 

This may also be something where an AOP framework might be useful, but I have not tried that solution.