Product Reviews


The road map for your .NET object development.

ORM.NET is an object-relational mapping product for Visual Studio .NET users. Rather than starting with an abstract object model (as does, for example, Visio Enterprise Architect with its ORM capabilities), ORM.NET assumes that you've already built the relational database you need to hold your business information. It then uses that database to build an entire data access layer for your application in C#.

ORM.NET is trivially easy to use. Connect to your database, click the "Generate Data Layer" button, and compile the results. Then you can start writing code like this:

DataManager dm = new DataManager(Config.Dsn);
Customers c = dm.NewCustomers("DC Company", "DCCOM");
c.City = "Endicott"; c.Region = "Washington";


ORM.NET builds the complete set of objects you'll need, and insulates you from the physical database. In addition to wrapping up all your tables, it lets you easily call stored procedures with just a thin wrapper. Tables can be designated as read-only lookup tables, and you can do quite a bit of customization before embarking on the data layer generation process.

There are a lot of code-generation products for VS .NET these days. ORM.NET is certainly one of the easiest to use, and for placing a data access layer on top of a relational database it seems to work quite well. You can download a 14-day trial from the company's Web site to try it yourself.

About the Author

Mike Gunderloy, MCSE, MCSD, MCDBA, is a former MCP columnist and the author of numerous development books.

comments powered by Disqus

Reader Comments:

Tue, Dec 30, 2003 Anonymous Anonymous

I'd prefere DataObjects.NET - there are some disadvantages agains ORM.NET, but the overal feature set looks much better.

Mon, Sep 22, 2003 Anton Ukraine

ORM.NET on the right way! It is help to make bridge between conceptual modelling which is perfectly done with ORM and database design. I see open opportunities to look over rules and constraints to generate advanced sevices to work with generated database model. We should have possibility to adjust generated stufff to use with any other persistence framework if we wish.

Fri, Aug 8, 2003 Anonymous Anonymous

Olero says 'We think ORM is Excellent'.

Hmm, good for a small development maybe, but for mission critical business apps...forget it.

Fri, Aug 8, 2003 Anonymous Anonymous

Poor performance (not even MS uses datasets in their O/R efforts...) and immature feature set. This tool is easy to get started with and quick to grow out of. ORM.NET should be called an object to dataset mapper, anything else is bogus!

Sat, Aug 2, 2003 Anonymous Anonymous

We've been using Objectz.NET - - for one thing it's free, supports a ton more options like inheritence and caching - and it has saved our project untold development hours.

Thu, Jul 10, 2003 Anonymous Anonymous

gotta luv the java jerks spewing their drivel - for a product in its 1.x phase, it rocks.

Fri, Jun 6, 2003 Anonymous Anonymous

Interesting to see a toy getting such a good rating. Missing support for inheritance, dynamic extension of the object model at program startup time and caching make orm - something that people in the java world actually would laugh at.

Sat, May 24, 2003 Olero Software Anonymous

PLEASE NOTE: ORM.NET is only $495.00 per developer license.
Sorry to hear the last Anonymous user says "It Sucks". Some details about why would have been nice :).

We may be a little biased but we think ORM.NET is Excellent!.

Fri, May 16, 2003 Anonymous Anonymous

It sucks

Wed, Apr 2, 2003 Anonymous Anonymous

Better than any of the other O/R and/or DAL tools I have looked at. We will actually end up using ORM.NET on our current project.

Sun, Mar 30, 2003 Anonymous Anonymous

Good OO DAL architecture.

Sat, Mar 29, 2003 Anonymous Anonymous

Saved me a ton of time.

Add Your Comment Now:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Please type the letters/numbers you see above

Redmond Tech Watch

Sign up for our newsletter.

I agree to this site's Privacy Policy.