Hello, Most of the points you have listed would not impede NHibernate working well, if the application mappings are well designed. And it will then be more efficient to develop with NHibernate if you want a domain model rather than a list of "table classes". But so I advise to have some experiences using NHibernate: learning to use a new tool on a complex scenario is no easy feat.
Beware of composite primary keys: they require some easy but specific handling in NHibernate (see http://nhforge.org/blogs/nhibernate/archive/2010/06/30/nhibernate-and-composite-keys.aspx for example; but I would recommend mapping composite key as a component by the way). For starting points, well, I really think it would be better to have some simpler project to start with and learn to use NHibernate with them. You can also use some "recipes" from Jason Dentler "NHibernate 3.0 Cookbook". (The first ones are good starting points imho, the following ones are more and more specific to special use cases.) Regards. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
