ORM Frameworks for Visual Studio 2005

11 Nov 2005 3:33 AM

sp00ky

Can anybody make suggestions as to which ORM/Persistance frameworks
work well with ADO.NET 2.0 and Visual Studio 2005? I've been using
ORM.NET since it was open sourced and have been very pleased with it.
It doesn't appear to be actively maintained even though it is/was a
first rate product. So I'm in the market once more for an ORM
framework, one that is designed to work with the Visual Studio 2005.
Any suggestions would be welcome.

Thanks

11 Nov 2005 9:10 AM

Frans Bouma [C# MVP]

sp00ky wrote:

> Can anybody make suggestions as to which ORM/Persistance frameworks
> work well with ADO.NET 2.0 and Visual Studio 2005? I've been using
> ORM.NET since it was open sourced and have been very pleased with it.
> It doesn't appear to be actively maintained even though it is/was a
> first rate product. So I'm in the market once more for an ORM
> framework, one that is designed to work with the Visual Studio 2005.
> Any suggestions would be welcome.

We support vs.net 2005, though not all new features of .NET 2.0 are
supported yet. You'll find many O/R mappers out there which are in that
same boat.

Frans

--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

11 Nov 2005 2:10 PM

David Browne

Show quote

"Frans Bouma [C# MVP]" <perseus.usenetNOSPAM@xs4all.nl> wrote in message
news:xn0e9m19s4aoyz002@news.microsoft.com...
> sp00ky wrote:
>
>> Can anybody make suggestions as to which ORM/Persistance frameworks
>> work well with ADO.NET 2.0 and Visual Studio 2005? I've been using
>> ORM.NET since it was open sourced and have been very pleased with it.
>> It doesn't appear to be actively maintained even though it is/was a
>> first rate product. So I'm in the market once more for an ORM
>> framework, one that is designed to work with the Visual Studio 2005.
>> Any suggestions would be welcome.
>
> We support vs.net 2005, though not all new features of .NET 2.0 are
> supported yet. You'll find many O/R mappers out there which are in that
> same boat.
>

I don't know what the state of the art is here, but I'd especially want to
find an OR mapper which leverages nullable types. These will give you much
better fidelity between your in-memory objects and your database rows.

ADO.NET has limited support for nullable types, so there's a great
opportunity for ORM Frameworks to leverage them to simplify the
representation of nullable database columns in the application tier.

class EntityFoo
{
int id;
DateTime startDate;
bool startDate_isnull;
string name;
bool name_isnull;

...
}

becomes

class EntityFoo
{
int id;
DateTime? startDate;
string name;

...
}

With the simple, consistent convention that "null means NULL". A null in
the application tier is used to model a NULL in the database.

David

12 Nov 2005 1:11 PM

Frans Bouma [C# MVP]

David Browne wrote:

Show quote

>
> "Frans Bouma [C# MVP]" <perseus.usenetNOSPAM@xs4all.nl> wrote in
> message news:xn0e9m19s4aoyz002@news.microsoft.com...
> > sp00ky wrote:
> >
> >> Can anybody make suggestions as to which ORM/Persistance frameworks
> >> work well with ADO.NET 2.0 and Visual Studio 2005? I've been using
> >> ORM.NET since it was open sourced and have been very pleased with
> it. >> It doesn't appear to be actively maintained even though it
> is/was a >> first rate product. So I'm in the market once more for
> an ORM >> framework, one that is designed to work with the Visual
> Studio 2005. >> Any suggestions would be welcome.
> >
> > We support vs.net 2005, though not all new features of .NET 2.0 are
> > supported yet. You'll find many O/R mappers out there which are in
> > that same boat.
> >
>
> I don't know what the state of the art is here, but I'd especially
> want to find an OR mapper which leverages nullable types. These will
> give you much better fidelity between your in-memory objects and your
> database rows.
>
> ADO.NET has limited support for nullable types, so there's a great
> opportunity for ORM Frameworks to leverage them to simplify the
> representation of nullable database columns in the application tier.
>
> class EntityFoo
> {
>   int id;
>   DateTime startDate;
>   bool startDate_isnull;
>   string name;
>   bool name_isnull;
>
>   ...
> }
>
> becomes
>
> class EntityFoo
> {
>   int id;
>   DateTime? startDate;
>   string name;
>
>   ...
> }
>
> With the simple, consistent convention that "null means NULL". A
> null in the application tier is used to model a NULL in the database.

Ok, though as I said, I'm not aware of any mainstream O/R mapper
frameworks which already support natively .NET 2.0 nullable types. We
can do nullable types with the .NET 1.x nullable types 3rd party lib
but it's far from optimal.

Frans

--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

25 Nov 2005 10:18 PM

Paul Gielens

Paul Wilsonâ€™s WilsonORMapper (http://www.ormapper.net) supports both Generics
and Nullable Types.

###
Best regards,
Paul Gielens

Visit my blog @ http://weblogs.asp.net/pgielens/

Show quote

"sp00ky" wrote:

> Can anybody make suggestions as to which ORM/Persistance frameworks
> work well with ADO.NET 2.0 and Visual Studio 2005? I've been using
> ORM.NET since it was open sourced and have been very pleased with it.
> It doesn't appear to be actively maintained even though it is/was a
> first rate product. So I'm in the market once more for an ORM
> framework, one that is designed to work with the Visual Studio 2005.
> Any suggestions would be welcome.
>
> Thanks
>
>