tag:blogger.com,1999:blog-7442262522977329981.post5226534026704345722..comments2011-05-25T12:10:32.002-05:00Chris Ammermanhttps://profiles.google.com/118440544456036580001noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7442262522977329981.post-29674485019804313472011-05-25T12:10:32.002-05:002011-05-25T12:10:32.002-05:00Very interesting post! Along the lines of one of our conversations, what you described sounds like a "meta-factory" (if such a term exists!). :-) My opinions have shifted to and fro regarding the proper role of IoCs - and I think I'm currently a minimalist. I've used StructureMap the most, but when it comes down to it, then thing that strikes me about a lot of the IoC debate between friends of mine here is that the advantages many of them tout end up causing them to tightly couple their systems to a particular IoC container, which I find ironic. I think you've made some interesting points, though, and have definitely got me thinking through it afresh. I kinda like the challenge the first commenter left - and if you do venture to build something, even as just an exercise, I would check it out since I'm bound to learn a lot from it!. Only other thing I would say is that while I think scanning is a separate responsibility from IoC, the two concerns are very often used in concert to accomplish a greater task - I know Alex and I have handled some service-spin-up operations to scan and register even complex dependency chains by convention (or specific scan instructions) - that has made development much more efficient for us....Jimhttp://ifandelse.comnoreply@blogger.comtag:blogger.com,1999:blog-7442262522977329981.post-89929028944352058012011-05-24T16:51:47.280-05:002011-05-24T16:51:47.280-05:00I think you should write one.Anonymousnoreply@blogger.com