Date parsed: 04/10/2007 17:19:35
Date: Fri, 05 Oct 2007 00:19:35 -0700

On Oct 5, 7:49 am, AliRezaGoogle <asemoo...@yahoo.com> wrote:
> Currently there are some good ORM tools like NHibernate and LLBGL.
> Microsoft is working on it's own one ( I think it's name is
> EntitySpace) but not released yet.
> I want to know members idea about selecting one of these ORMs:
>
> --Should we wait untill Microsoft release his own ORM? ( and maybe
> after two or three years again releases another one and we have to
> throw our experiences away and styart to learn new one?)
> --Choosing current ORMs is nice? (Does for example NHibernate remain
> with .NET forever with support? What about future release of .NET? Is
> there any quaranty that future features of .NET remain compatible with
> current ORM frameworks? )

Well, firstly I have no experience of LLBGL, so can't talk about that.
NHibernate appeals to me due to it being open source, and I have had
very positive experiences of its Java cousin.

As for Microsoft: LINQ to SQL will be released with .NET 3.5, but that
only works with SQL Server and isn't as flexible as it might be. It's
good for rapid development, but I suspect that most serious projects
will wait until ADO.NET 3 is released with SQL Server 2008, and with
it LINQ to Entities.

Whichever you choose, don't underestimate the importance of LINQ. Even
if you don't plan to use C# 3 yet, you're likely to in the future, and
LINQ is *lovely* where you can use it. (In some cases you may have a
query which can't be expressed in LINQ, but that's okay.)

As for backward compatibility: I wouldn't expect MS to release a
version of .NET which breaks NHibernate or other libraries, and if it
*does* I'm sure the NHibernate community will rally round to make the
necessary changes.

Jon