Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I would definitely say go with fluent-nhibernate. Just be aware it may not necessarily be as smooth a ride as you would hope. </p> <ol> <li><p>Regarding version dependency</p> <ol> <li>I have had a 'reverse' dependency issue when upgrading to a new version of FNH required me to upgrade to a new version of NH (2.0 to 2.1 I think). This was not a major issue for me.</li> <li>I just recently (this morning) dropped NH 2.1.1 into the FNH 1.0 RTM (this is distributed with 2.1.0) without any dramas (yet). </li> </ol></li> <li><p><strong>Edit: Since writing this post FNH has matured substantially to the point where I do not think this is a real issue anymore</strong> <strike>Mapping support - some mappings are not yet possible with fluent nhibernate. However, this is NOT a reason to avoid FNH as hybrid fluent-xml mappings allow you to fallback on traditional xml in the event of fluent being unable to map it (although this is only on per-class granularity). Examples of mappings:</p> <ol> <li>Cannot yet map fields - <a href="http://groups.google.com/group/fluent-nhibernate/browse_thread/thread/a7787927dafd23a/84ce2616946a18d7?lnk=gst&amp;q=fostandy#84ce2616946a18d7" rel="nofollow noreferrer">http://groups.google.com/group/fluent-nhibernate/browse_thread/thread/a7787927dafd23a/84ce2616946a18d7</a></li> <li>Cannot map some times of dictionary <a href="http://groups.google.com/group/fluent-nhibernate/browse_thread/thread/d38b6c72250cd2fb" rel="nofollow noreferrer">http://groups.google.com/group/fluent-nhibernate/browse_thread/thread/d38b6c72250cd2fb</a> - actually from what I gather this functionality exists but is not in the mainline yet.</strike></li> </ol></li> <li><p>Compound complexity factor. From the sounds of it you will be learning both FNH and NH at the same time. For the majority of fairly simple applications this is fine - infact FNH is often so good that you need to know fairly little about the hbm.xml mappings. But if you want to go do something reasonably complex, it will rarely work the first time round and you are left wondering if it is a PEBKAC, fluent or NH issue. More often than I'd hoped I ended up writing the traditional xml mappings (of course, you are doing this anyway, but it would have been preferable not to expend more effort than necessary fiddling with fluent first).</p></li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload