views:

231

answers:

2

If so, have you run into any immediate gotchas?

+2  A: 

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

lomaxx
+3  A: 

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.

Matt Hinze