This comes from ASP.NET 2.0 Website Programming—Problem – Design – Solution by Marco Bellinaso (ISBN-13: 978-0-7645-8464-0)
Quote:
“Some people have developed tools called ORM (Object Relational Mappers) utilities, which can make it easier to map database tables, views, and other relational objects to an OOP class. They can dynamically explore the database’s schema and create the wrapper custom entity and domain object classes for you. Some of them work at design time to automatically produce C# classes you can compile into your application, and others work at runtime to perform this mapping function on-the-fly. But sometimes they don’t work as well as we’d like them to, and there can be a considerable learning curve to set up these tools to work with your particular database and usage requirements. Some of the most popular tools for .NET developers are NHibernate (nhibernate.sourceforge.net [open source]), EntityBroker (www.thona-consulting.com/content/products/entitybroker.aspx [free community version and commercial versions available]), and LLBLGen Pro (www.llblgen.com[commercial]). A simpler tool for small to mid-size systems is Paul Wilson’s ORMapper (www.ormapper.net). I decided not to use these tools in this book because I generally prefer a custom-designed mapping solution specific to each application, but I can see that these tools may be your best alternative in some cases. If you have been contracted to develop a new system that will later be maintained by corporate developers, you’ll have to get their buy-in before selecting any third-party tools because some companies have policies that prohibit the use of “unapproved” tools they haven’t officially sanctioned.”
Well,well, strange this comes to my attention exactly now, when I’ve just written two posts on this matter…
