Based on your experience, how many of you would recommend fluent NHibernate over Nhibernate way of doing things for my new project? -

I just want to make a quick choice to see if Flint Enhrenet has been well received or if there are many Problems I like Nhibernate but I certainly look at the problem of mapping XML.

So, I look forward to some members of the community for insights and help me get one over one.

I am not considering either linq2sql or entity framework at this time.

I like Flute Nabbernet and I think that if you are going to start a new project then it is mature enough. By using this on a new project, the Fluent NBiberate project should be mature as your progress. There is a possibility of breaking the changes (recently happened with the mapping of the conference) but you should be able to deal with them. I had some problems with mapping but this project is very favorable for bug reports and most of the expectations

• XML Mapping - Standard Maintenance Headache of NHibernate is well known but the advantage is that your address L Adding still Fluant the configuration options that can reduce the use of paid access to all configuration options by NHibernate (at less the last time I noticed). Therefore, if you are anticipating some crazy mapping, then you may want to consider this option.

• Standard mapping - provided by Fluent, you can create mapping through code and is very good for refactoring and authoring. To say a lot about it, in my experience, otherwise it works fine and there is a big improvement on the XML option.

• Auto mapping - provided by Fluent allows you to mapping object properties by the conference and it automatically tries to create mapping. This is a good idea But I think it's still going to do something. I am currently using this mapping method and it works fine, but I have stopped writing too many conventions and have to specify the object relation which it does not realize is that it is a lot of effort from standard mapping Is saved.

Liquid NHibernate also provides good test assistants to test your mapping and some configuration APIs that can make NHibernate easier to configure. Overall, this one Is a good project and it provides some good additional functionality to NHibernate.

---

Edit:

One more thing to note: If you start FluNet with NHibernate and decide it will not work for your scenario You can easily migrate back to XML mapping. The selfish NHibernate makes it that allows you to export mapping and you can use those exports to lose mapping functions, which lose the mapping work you've already done.