http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Isn't some of the point of the IoC to have the control outside of the code and in configuration files that can be edited without require code to be rebuilt? The attribute approach is interesting - ie. same approach as using something like NHibernate attributes instead of NHibernate mapping files. Again though, as with above, if I want to plug in a new component in place of an older one - wouldn't I have to goto the code and change the attribute, requiring a rebuild, etc... ? Outside of that concern, I think tools to build the xml is the next big step. ie. similiar to what Hayden is doing with his Repository injection. A GUI tool to edit and build configuration files for Windsor/Spring would be fantastic. It could validate the files, etc... That is just another option I would consider. If the tool could do the reflection for the assembly and namespace, pick up the constructor values etc.. it would speed it up and make it easier to manage. Throw in a GUI form with the tool that showed draws lines showing the dependency relationships would add even more value. When someone else comes to review the code, they can see the 'mappings' to help them understand the system better than attempting to muddle through 1000 lines of xml. Xml is like assembly to me :) http://ayende.com/2777/convention-over-configuration-structured-approach#comment1http://ayende.com/2777/convention-over-configuration-structured-approach#comment1Thu, 20 Sep 2007 21:31:23 GMT