However, I completely understand the concern some people have with intermingling their infrastructure with higher layers of their application. I think this largely stems from frameworks requiring the use of ugly attributes, which need to carry all sorts of information beyond simple tagging. I’ve tried very hard to avoid that sort of thing in Ninject. :)

Thanks for the comment!

Saw this on DZone and found it interesting.

Attributes for injection are a good thing IMO. Coming from a Java-side, they haven’t always been around. Pre-”annotations”, most Java DI frameworks relied on wiring of dependencies in XML, which was tedious, but ultimately pulled all of the wiring out into configuration. That meant it could live outside the code, keeping the code cleaner and more abstract, and also allowing you to switch things out without having to recompile anything.

Once annotations and Guice hit the scene, this really took a backseat because you could introduce typesafety into the mix.

You may be interested to check out this blog entry for the skinny on what’s “bleeding edge” in this arena ATM:

http://solutionsfit.com/blog/2007/11/09/thoughts-on-webbeans-and-stereotypes/