Has anyone moved to NHibernate 2.0 in a production environment?
-
09-06-2019 - |
Question
If so, have you run into any immediate gotchas?
Solution
Yes..
Here are the gotchas (a more detailed discussion here):
Flush after Delete
Expression namespace change to Criterion
It wasn't a tough migration, and it won't be for you if you have good test coverage.
OTHER TIPS
We have moved to 2.0, but only for new development (not migrating old to new).
The reason for this was there are a couple of breaking changes that are documented online and we didn't have the budget to fix it. The big ones for use were:
- Changed NHibernate.Expression namespace to NHibernate.Criterion
<nhibernate>
section is ignored, using<hibernate-configuration>
section (note that they have different XML formats)
Edit: There's a pretty good summary of the latest changes to NHibernate 2.0 on CodeBetter
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow