i understand your point of view. If you design a new solution from scratch 
you can use modern approaches like code first, But in the real world you 
sometimes have some limitations. For example, you have to use an existing 
database or the customer you are working for has a special team for all 
database affairs and doesn't allow developers to manipulate the database. 
In those cases you have to maintain config files which is a pain to do 
manually. Of course you can use template tools (like T4 for example), but 
then you have to write and maintain the templates for yourself. If you have 
a tool, which has all the knowledge of how to generate a configuration 
efficiently inside it is a high value for the user. He can concentrate on 
the business logic and don't have to spend much time with the annoying 
plumbing code for database access.

Regards
Klaus.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"nhibernate-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to