IoC container configuration
Posted
by nivlam
on Stack Overflow
See other posts from Stack Overflow
or by nivlam
Published on 2010-04-19T02:53:26Z
Indexed on
2010/04/19
3:03 UTC
Read the original article
Hit count: 655
inversion-of-control
|ioc-container
How should the configuration for an IoC container be organized? I know that registering by code should be placed at the highest level in an application, but what if an application had hundreds of dependencies that need to be registered? Same with XML configurations. I know that you can split up the XML configurations into multiple files, but that would seem like it would become a maintenance hassle if someone had to dig through multiple XML files.
Are there any best practices for organizing the registration of dependencies? From all the videos and tutorials that I've seen, the code used in the demo were simple enough to place in a single location. I have yet to come across a sample application that utilizes a large number of dependencies.
© Stack Overflow or respective owner