The last release candidate was unfortunately not the final one. Last Friday I silently released a new candidate, and since there seems to be no obvious error, it's not time to announce it (I had to retract a previous tentative to public RC4 for this reason).

This new RC corrects fourteen issues, two of them required non-trivial changes requiring a new RC.

Maybe the best news for all is that it is now possible to apply multiple OnMethodInvocation aspects on a single method, at least with target-site weaving. I have been shamefully so far too lazy to reconsider a limitation that no longer any rationale.

I was however quite satisfy to notice that most bugs had pretty small coverage, so I consider already the product as very stable.

Unless you guys come with a new high-coverage bug requiring non-trivial refactoring, this will be the final release candidate.

Happy PostSharping!


Dependency Injection is Dead! is the somewhat provocative title of an interesting post of Simon Ince.

Simon indeed proposes another approach: AOP-powered Dependency Resolution. The idea is to use aspects on fields or properties to resolve the dependencies on-demand, when the property or field value is retrieved. Technically, it would be enough to turn the old good [Dependency] custom attribute into an aspect.

I won't copy-paste Simon's stuff, so please read from the horse's feather on his blog.

A refreshing view on a topic that tends to become sanctified and therefore unchallenged in our community.

Even if this approach does not solve all the use cases of Dependency Injection, covers a lot of them in quite an elegant way. While it would be theoretically easy to use this approach with dependency injection frameworks (because dependency resolution is obviously one the major components of a DI framework, the other big one being the object builder), I noticed that Unity does not offer the functionality at the required level of granularity. A pity, which I have notified in illo tempore to the Unity team. Maybe some day wind will turn...

Happy PostSharping!


I have opened a special section of the forum for VIP community members. The objective is to share content with DNUG leaders, speakers, and technical writers.

Indeed, I've long looked for a way to make it easier for speakers to get something to show about PostSharp: some figures, some slides, or even whole presentations ready to be served. However, I needed some way to ensure that the same content will not be served twice to the same audience, and they the audience does not just get the same content as it can download from the web site.

The solution I found: make this content available to selected people only.

So if you are a user group team leader, conference organizer, speaker, technical writer -- or if you have any other good reason to get access to this content -- you can request membership in the VIP group. The VIP section is implemented as a protected forum in our message board, where downloads are simply attachments to the topic. Every time the content will be delivered somewhere, I'll add a post to the topic.

By the way, even if you get access to this section, you still need to respect copyrights and request for permission before publishing any non-trivial part of the content.

I just hope I don't frustrate tons of people because of that... Oh, if you want to see the content, why not ask your UG leader to organize something?

Happy PostSharping,