Who else is using / implementing / interested in AOP

# re: Who else is using / implementing / interested in AOP

Personally, I know what it is (ok, that sounded strange, as if I needed to validate that fact, but it was more just an answer to your question).

I've never been a big fan of AOP. While I do believe that there are benefits to it, I think that there are too many problems with it to make it viable (e.g. aspect ordering, weaving code into the middle of a method).

However, if you asked me about method interception, I am all for that. I think that is much more viable than AOP, and there are mechanisms to do that now (ContextBoundObject, as well as the sink architecture in Indigo). 11/18/2005 4:22 AM | Nicholas Paldino [.NET/C# MVP]

# re: Who else is using / implementing / interested in AOP

AFAIK AOP is implemented in .Net through creating custom controls along with extender providers. This allows a work-around for supporting multiple inheritance and is pretty common among custom control developers.

Google

aspect oriented programming extender provider

for more information. 11/18/2005 5:15 AM | Brian

# re: Who else is using / implementing / interested in AOP

John,

Have you checked out the interception model in WCF? It's going to be a little better than deriving from ContextBoundObject, since it forces you to define your contract (and interface) and doesn't force you to burn your base class.

I agree with your comments about wasting the base class. It's a shame that you have to derive from something (I don't think that you should have to, this should have been implemented better on the CLR level, IMO).

However, once WCF comes along, I think this will be the easier way to handle method interception.

- Nick 11/21/2005 6:23 AM | Nicholas Paldino [.NET/C# MVP]