A
Anonieko
Pigsaw said...
"You don't want to hard code dependencies into your classes, because
then you can't test them without relying on the dependent classes. So
you "inject" those dependencies simply by setting them as properties -
possibly in the constructor, possibly with setter methods. And it
becomes all the easier if you have a little container which manages
how to configure those dependencies (properties) before they're
injected (set). "
Any shorter one?
"You don't want to hard code dependencies into your classes, because
then you can't test them without relying on the dependent classes. So
you "inject" those dependencies simply by setting them as properties -
possibly in the constructor, possibly with setter methods. And it
becomes all the easier if you have a little container which manages
how to configure those dependencies (properties) before they're
injected (set). "
Any shorter one?