Xml on large project is not sexy and not productive :)))) We had our own ORM on a large project and it allowed both, attribute and xml mapping. Nobody ever used xml for 5 years because it is yet another pain point when you do refactoring. I know, attributes create unwanted dependency of DTO on ORM, but in practice it did not cause as much problems as xml config.
Vadim. On Jul 14, 11:11 am, Frederic <[email protected]> wrote: > A visual designer on a very large project would be like using an Iphone > to code the business logic : sexy, very attractive but not productive. > > Le 14/07/2010 19:58, Fabio Maulo a écrit : > > > designer but then the framework itself does not fit the exigence of > > "many of our" applications. > > Because I'm not a good Picasso, I prefer to write code (C# or XML > > mostly). -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
