I set up my WindsorContainer by sub-classing, and performing registrations via FI-code within the constructor. The constructor takes an XmlInterpreter as a parameter and passes this down to the base-class, which means I can do the bulk of my registrations in code, and override settings by using the config file (as long as I remember to name all my components - which I do :-) ).
That said, I've never had to actually _use_ that in production - but it's nice to have! Regards Pete On Sep 10, 7:06 pm, Nathan Stott <[email protected]> wrote: > I disagree. Binsor, on several occasions, has saved me a lot of headache by > allowing me to reconfigure my apps in production without having to recompile > them. Windsor Fl does not allow for this. > > > > On Thu, Sep 10, 2009 at 2:02 PM, Ayende Rahien <[email protected]> wrote: > > To be absolutely honest, with the Windsor FI, I am not sure there is a lot > > of place for Binsor. > > > On Thu, Sep 10, 2009 at 8:59 PM, rg <[email protected]> wrote: > > >> Please save the Binsor! > >> R --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
