With the upcoming DLINQ and other LINQ technologies, Microsoft is coming up with an elegant OR mapping solution of their own. However, until .NET 3.0/3.5 becomes mainstream enough (1-2 years) there are existing OR mappers (NHibernate, Neo, etc.) to choose from.
I'm currently developing with NHibernate as part of an R&D project at the animation studio I work at. The application is an extension of asset manager and, when complete, will use NHibernate to adapt the exisiting database, share tables (Users, Episodes, Shots, Comments, etc.) as well as access its own specific tables. In other words, its a new application with legacy ties.
The pros of NHibernate are the relative ease of use once everything is configured and mapped. The cons are that it can take a long time to get configured correctly. Benefits like self-management, lazy-loading, and inheritance comprehension are just a few of the features that really have me hooked.
What I want to know is, what other OR mappers have Niners dealt with. Which did you like, which did you not like, which did you downright hate? Basically I'm curious to get a cross section of the OR mapping "market", if you will.
Silverlight: Geek Profiles – Scott Guthrie
WindowsClient: New WPF Showcase Addition: Enterprise
