Anything new on AOP in .NET land?

As you might remember, I have blogged about AOP in .NET earlier (here, here, and here). I guess it's time for an update.

This summer I saw that Eric Gunnerson from the C#-team blogged about AOP here. As I said, this post is a few months old and Eric is no longer with the C#-team, but even so, the conclusion I draw from the post is that we won't be seeing any AOP support in C# in the near future...

I heard that Anders Hejlsberg received many requests from developers to extend the semantics of partial classes in .NET 2.0. I'm actually one of them. We discussed whether making it possible to use a fragment of code in several classes, by slightly extending the partial classes feature, would be a good thing. It would be like poor man's AOP Introduction - static, but fine for now, especially with some editor support. Adding an aspect in the form of a couple of methods and/or some data to several classes is called "Introduction" in AOP language... Yep, that's right. AOP doesn't have to be about interception! That's pretty shocking considering the usual logging examples, right?

Talking about how AOP isn't only for logging, I recall the preparations for a workshop around a year ago. There were loads of design problems up for discussion. Rickard Öberg said, and proved, that all of these problems could be solved with AOP and that totally blew my mind! Even though I don't see AOP as the silver bullet, it's definitely something I'd like to have in my toolbox!

Oh, and finally, I just read here that John Lam has changed his mind and now thinks AOP is interesting again.