I think that certainly depends on your needs. In my experiences, at the first time I used to put Windsor config in app.config because I read that I can configure things without recompiling app, just like what you said. But then, after a period of experience and evaluation, I observed when I changed the config, I also had to modify the code. *I haven't found a scenario where I can change to config only without recompile app. *Also, configuring things in app.config is bit pain in the ass since I don't have compile-time checking, especially when it involves generic types configuration. Based on those reasons, I decided to move all config from file to code. And importantly, I feel better now :D.
-- Regards, Maximilian Haru Raditya On Wed, Jun 29, 2011 at 5:03 PM, bdaniel7 <[email protected]> wrote: > Hello, > > Is there a recommended (or best) way to configure Windsor? > > I think that xml config has the advantage that I can just deploy the > "new" implementations, modify the bindings in the xml and restart the > app. > While with code I have to recompile and redeploy the entire app. > > > Your thoughts? > > Daniel > > -- > 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. > > -- 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.
