Offer a Simple ORM on .NET - Design to Support Legacy Applications

I have been instructed to support a bunch of legacy applications using heavy stored procedures created before '05, when there was no ORM. The developers who work with me do not know Entity Framework and LINQ and do not want to learn.

Is there an ORM in .NET that provides a simple object interface to existing database tables and possibly stored procedures?

I am very pleased if it allows me to encode multiple rows to get a class for each table, and it has properties corresponding to the data in each column, as well as some methods or properties for resolving a foreign key / many-to-many relationship - go ahead and back.

For example, saving employee and department records

Employee e = new Employee("John", null);
Department d = new Department("QA");
d.save();
e.department = d;
e.save();

without writing SQL INSERT statements.

EDIT: MS SQL Server 2008

+5
5

Rob Conery Massive. . , .NET 4.

+4

PetaPoco, ORM .

:

PetaPoco , Rob Conery Massive, POCO. , , SubSonic/Linq, Linq CodingHorror.

, , , .NET 3.5 / Mono 2.6 (.. ). Massive 400 , , - .

+3

Subsonic .NET 2.0, . , , .

0

NHibernate - , Java Hibernate, , SubSonic. SubSonic Linq, , , "ActiveRecord". , , , . SubSonic , , , Google . , , .

0

All Articles