I had a look at DLinq, and there are some cool concepts there, beyond the language intergration.

Specifically, I like the ability to get generic collections from the get go.

Beyond that, there was a nice concept of a typed collection of EntitySet<T> & EntityRef<T>, both of which accept delegates for adding/removing from the collection, so you do:

posts = new EntitySet<Post>( delegate(Post p) { p.Blog = this; }, delegate (Post p) { p.Blog = null; })

And the reverse (although you obviously going to need only one of them)

blog = new EntityRef<Blog> ( delegate(Blog b) { b.Posts.Add(this); }. delegate(Blog b) { b.Posts.Remove.Add(this); })

Any interest in doing them for NHib?
What is the status for .Net 2 ? ISTR talks about it several months ago, but I can't recall anythign concrete.

At the very least, I think that suporting strongly typed collections is a must. What is needed to add those?

Hibernate 3 has UserCollectionType which can be used as an inspiration, or maybe just copied. It will require the user to implement his own collection wrapper though.

Actually, I was talking about providing NHib versions of:

IList<T>
ISet<T>
IDicrionary<T>

etc.

I took a look in NHibernate.Collections, and it seems to be pretty straight forward to do it.
Anything I needs to watch out for?

We just haven't figured out how to integrate it nicely into build process and into NHibernate itself, so that NHibernate would build and work on both .NET1.1 and .NET2.

I've code (Rhino Mocks) that I maintain for both .Net 2 & 1.1

I'm mainly doing something like:

#if dotNet2
dot net 2 coolness
#endif

And then I add a define in the NANT to add dotNet2 for the build if it's compiling for .net 2