DI and IOC
The text of this article is not in this database — only its details are. Read it on the old site: DI and IOC
1 Comment
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
Loading
The text of this article is not in this database — only its details are. Read it on the old site: DI and IOC
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
steve KrizanovicPosted May 25, 2011, 1:19 AM
Hi, Can you please explain the purpose or benefit of applying this pattern. I dont really understand why you would want to decouple naturally coupled component, or did you use the customer / address as an example only? I think by decoupling the code in this fasion and allowing users to customise the dependencies to be injected through the config, we are opening up a world of hurt. In the customer / address example, say a user does not realise there is a dependancy there and removed address. There is no recompiling, no complie time exceptions as everything is decoupled anyway, just an application which crashes at runtime. Surely this is not beneficial when developing an application.