I am trying to build nhibernate using .net 2.0. beta2. I have seen posts http://sourceforge.net/mailarchive/foru ... m_id=29446 . However, it looks like nhibernate was build using nant 0-85 rc3 that does not support .net 2.0.So my steps were the following:

1.Download nant latest nightly build that supports .net 2.0 beta 2 - http://nant.sourceforge.net/nightly/latest/nant-bin.zip
2.Download latest DynamicProxy source from svn repository - https://svn.castleproject.org/svn/castle/trunk/
3.Build release version of DynamicProxy.
4.Download nhibernate source from cvs repository - path -:pserver:anonymous@cvs.sourceforge.net:/cvsroot/nhibernate ,module nhibernate
5.Change nhibernate.build file, rename every “1.1” inside target <target name="set-net-1.1-runtime-configuration"> and in <call target="set-net-1.1-runtime-configuration" /> string to “2.0”.
6.Create additional directory “2.0” in the nhibernate/lib folder. Then copy all files, except DynamicProxy.dll, from nhibernate/lib/1.1 folder and new DynamicProxy.dll built on step3 to this folder.
7.Build nhibernate.
8.Run tests with nunit 2.2 (also configured to support .net 2.0 beta 2).

All test succeeded except the following two:

NHibernate.Test.FooBarTest.FindByCriteria :
TearDown : Test didn't clean up after itself

NHibernate.Test.NHSpecificTest.NH257.Fixture.ManyToManyTableCreationScript :
String lengths differ. Expected length=107, but was length=98.
Strings differ at index 13.

expected:<"create table users_in_groups (group_id INT not n...">
but was:<"create table Party (Id INT IDENTITY NOT NULL, pa...">
------------------------^

If you use debug version of DynamicProxy.dll (step 3), nhibernate tests will fail with “… DynamicProxy…duplicated..” exception.

Those failures are strange, but should be harmless. I don't have .net 2.0 currently to investigate. Don't use the debug version of DynamicProxy, it only allows for one proxy class to be generated.

Further to the original post, I've run the NUnit tests for NHibernate v1.0.2 with the release version of .NET 2.0 (i.e. v2.0.50727) and the same two tests fail.

My question is:
Are there any plans to investigate and correct this?
-----
As an aside for information to others:
I upgraded my .NET 2.0 solution to use NUnit v2.2.7 as well and TestDriven.NET v2.0.1545.0. The results are the same, there are still 2 failing tests.

Using NUnit GUI v2.2.7 reports 632 tests (620 run, 2 fail, 12 not run). There seem to be 3 "extra" tests reported by the GUI and not run!

This differs from the results obtained from TD.NET within the VS 2005 IDE which reports 618 passed, 2 failed, 6 skipped (a total of 626 tests). I think TD.NET is completely ignoring 3 tests attributed as [Explicit] so that would give a total of 629 tests with 9 skipped.

My benchmark tests with .NET 1.1 and NUnit v2.2.0 were:
NUnit GUI v 2.2.0 reports 629 tests (620 run, 0, failures, 9 not run).
TD.NET reports 620 passed, 0 failed, 6 skipped (total 626) [plus the 3 tests marked as [Explicit] makes 629 - the same number].

All tests are against MS SQL Server 2000, under Windows XP.

I have seen both of these problems. The FooBarTest failure is due to a bug in OuterJoinLoader.WalkAssociationTree - I posted the following summary of my investigation: http://forum.hibernate.org/viewtopic.php?t=957388

The other failure (if it's the one I'm remembering) is due to a bug in the test - it assumes a specific order of items in a list, but the list is populated by enumerting a Hashtable, so the ordering in undefined and different between CLR 1.1 and 2.0.