Thanks for sharing - checking out the code as I'm writing this.

One question though: what was the motivation for writing your own ORM? I can understand that Castle's ActiveRecord might be limiting in some scenarios but why not use NHibernate directly without the AR abstraction layer?

does it support LINQ?

where is the rest of the documentation?

Looks like this is doomed to fail. Imho there is nothing new. It's more or less just the same old orm. What's the catch?

Needless to say, people are currently moving away from simple ORMs. Content Repositories with standardized APIs like JCR looks like the way of the future. In MS platform there isn't JCR compliant implementation, but SharePoint might be the standardized repository for .NET applications in the future. Also the NoSQL movement is raising their heads with cloud services supporting the ideas alternative to SQL. Document DBs (XML DBs), Graph DBs, Key-Value Stores, etc. A Repository can abstract the underlaying storage engines - ORMs are too tied to storage engine. Well, you can always build repository abstraction on top of ORM (or ORM can help building one).

But don't let these words slowing you down. Who knows, you will come out with something beautiful in the end. It's a long rocky road to walk. First steps are usually easy.

Hi Sune

I share your frustration with a lot of the existing ORMs out there. I am currently using SubSonic for a project I am working on, you might want to take a look if you don't know it already..

http://subsonicproject.com/

Have a nice day!
- C