.net - Should I use Spring.Net AOP Throws advice? -

background

I have a component that provides some CRM services - specific CRM with me Is a special CRMadapter that implements my IGRRCR interface.

Another component exposes CRM functionality through normal CRM IGeneralCRM and uses Spring.Net to inject specific CRMAdapter to provide such functionality.

Question

I want to be able to catch an exception if specific CRM components fail. Should I apply Spring.Net AOP advice to complete this or do I am on the engineering of the problem because what I have to do is to catch the exception only.

Is there a profit or the other way?

It really depends on what you want to do with the exception. AOP is amazing, but leads to complex configurations and often leads to an overkill.

Where AOP shines, many objects have the ability to argue to deal with the same business crossover. In your case, you show that you are working on the same implementation, so I will just ask to try to catch it for now.

If you think that you have the same logic as many ways and objects, then AOP is a better solution.