Glad to hear that several people are working with the latest versions without problems.
In my case, I tried to migrate a working application directly from FNH 1.0 to 1.3, and it broke horribly.
Main problems I ran into:
- a bug in FNH that failed to automap deeper levels of inheritance (issue #113, patch submitted, but not merged yet)
- a breaking change with the NH 3.2 byte code provider that now requires all properties to have a "set" method (I have dozens of get-only properties in my object model)
Even after resolving these problems, I found my collections were not being hydrated properly any more, so I rolled back to FNH 1.0.
-Tom