I like the Convention based approach with configuration values inside the XML. There are things that should be in XML (like configuration parameters) and there are things that don't belong there (like some internal classes nobody has business rewiring after deployment).
Convention based means that you don't have to register every class manually but that you define conventions on where classes get picked up automatically by the container. Ayende seems to be very fond of that approach with NHProf and I clearly see the benefit there. greetings Daniel On Thu, Sep 10, 2009 at 5:35 AM, Tiendq <[email protected]> wrote: > > Fluent is cool but I'm still personally like XML registration file. > > On Sep 9, 5:06 am, olcay şeker <[email protected]> wrote: > > how faster you guys!!!! many thanx.... > > > > On 9 Eylül, 01:03, Ayende Rahien <[email protected]> wrote: > > > > > > > > > It is already therehttp:// > using.castleproject.org/display/IoC/Fluent+Registration+API > > > > > On Wed, Sep 9, 2009 at 1:01 AM, olcay şeker <[email protected]> > wrote: > > > > > > is there any schedule to add fluent interface within windsor? like > > > > ninject or AR declaring type bindings with attributes instead of > > > > xml is easier..... > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
