The Castle Project includes a data model solution which uses NHibernate as the base layer. It operates on attributes, much like NUnit, and generates the NHibernate mappings on the fly.

http://www.castleproject.org/index.php/ActiveRecord:Reference_Documentation

http://www.castleproject.org/index.php/ActiveRecord_Generator

That's an interesting project... But I don't know how many people will learn it instead of going straight in NHibernate (with basic tools like code generators)

My main concern is that its mapping is based on attributes from Ruby on Rails AR (instead of NHibernate.Mapping.Attributes) and I am not sure that it is a wise decision :?
Read: http://forum.castleproject.org/posts/list/74.page

Castle is built by and for developers who like the Ruby On Rails framework but are paid to develop in .NET. Castle's ActiveRecord framework is designed to be an easy translation from its Ruby inspiration. As such, it is an excellent idea.

As NHibernate.Mapping.Attributes is modelled after the XDoclet attributes, its target audience is different. I fail to see how two attribute mapping frameworks is a bad thing when we can appeal to a wider audience. Besides, we're on the same team here!

Hey, you are talking like if .NET took the place of VB6 :D

I understand the reasons of the choices behind this new project :)
But having two attribute mapping frameworks divide our available (precious ;)) spare time in two... :?
And after doing NHMA, I understand the potentials problems that you could have to face :D

Are you thinking about integrating it in VS.NET?

You're right there. Others have picked up the torch of AR now, so I'm really not distracted by it anymore.


That's really not my area. Hammett is doing the generator. If I had to guess, I'd say no.