It is important to understand that IoC is just a pattern to help you to
achieve a more loosely coupled design (still subjective to call "better"
because of better being subjective). it is based on the fact that clients
don't need to know how to construct other systems just to consume them, so
this
Inversion of Control, it is used for better Domain Driven Design. Do
you know if it is better to use or not use with your experiences. Can
you share with us your toughts?
On 6 ago, 13:50, Tuna Toksoz wrote:
> What do you mean by IoC, for what purpose do you use it?
>
> Tuna Toksöz
> Eternal sun
Castle/Spring are 2 good ways of implementing IoC, but they are not
necessarily the only way.Using well known patterns you can easily implement
your own IoC for NHibernate.
I'm working on 3 projects that all use NH and the only tests that actually
require the database are the functional/acceptance
What do you mean by IoC, for what purpose do you use it?
Tuna Toksöz
Eternal sunshine of the open source mind.
http://devlicio.us/blogs/tuna_toksoz
http://tunatoksoz.com
http://twitter.com/tehlike
On Thu, Aug 6, 2009 at 7:48 PM, Guga Oliveira wrote:
> preffers without IoC.
>
> What is the o
