ORM Frameworks for Visual Studio 2005

  • Thread starter Thread starter sp00ky
  • Start date Start date
S

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
 
sp00ky said:
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.
Click to expand...

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

--
 
Frans Bouma said:
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.
Click to expand...

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
 
David said:
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.

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.
Click to expand...

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


--
 
Back
Top