Agreed. There aren't many situations where you can change xml config without modifying the code.
The only one that comes to my mind is when you want to switch 2 implementations of a service. If you have implemented both version in advance, simply change the relevant pieces of your config and you're done. Still the need to change the code (create extra implemntations) doesn't go away. On the other hand, you could implement new classes in separate assemblies. That way you won't have to recompile your core solution. It could save a reasonable amount of time in case of big projects. Personally I ususally leave xml configuration simply to override default dependencies and default values for injected properties. Vast amount of configuration goes to C#. As Maximilian wrote, you benefit from compile-time checking. It really does spare one a lot of frustration ;) Regards Tomasz -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-users/-/EbtPM7ItohkJ. 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.
