Both: Open source (e.g. nHibernate)
I like nHibernate, Wilson O/R M [0[ (aka WORM)-- at $50 with source, it's barely commercial] or the PuzzleNetwork framework [1] which includes nPersist. All have thier strengths and weaknesses, but I wouldn't quit any job that made me use one of them ;)
and commercial ... (e.g. DataExtend)
Don't do it... there are too many free options. I exclude LLBLGen as it's much more than a mapper... definately consider it strongly.
Or is it too early to consider early adoption for DLinq
That's your business model to drive... Linq for SQL (notice the name didn't even last!) in FINAL form is likely two years away... if you don't have to SHIP until then, go ahead and play there.
or Linq-based products?
If you want Linq, Otherwise consider a "clone". Me, I tried to mortage the time for when ObjectSpaces was going to come out and chose to play with WORM for a project. Now that Linq is the "current clear direction(s)" of Microsoft, the ObjectSpaces compatibility is a non-issue... but ask yourself if this can happen again. Will Linq really ship with an API that is "linq-based"? [0] http://www.ormapper.net/ [1] http://www.puzzleframework.com/ [n/a] http://musingmarc.blogspot.com/2006/01/best-keeps-on-getting-better-and-still_24.html -- "You hide yourself with sanctimony, I hide myself with narcissism." --T-Bone Burnett Marc C. Brooks http://musingmarc.blogspot.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
