List of Informed Opinions

After a period of lag behind Java, the offering of object-relational mapping for .NET is very rich. You can choose from open source or commercial, and from light to full-blown.

Be sure that your development team has clear ideas about the existing or desired database and OO architectures before selecting an object-relational mapping tool for your .NET applications.

The single most important trap to watch out for when choosing an object-relational mapping tool is "architecture by product." Architecture by product describes a set of symptoms I've seen in many p

The most important thing is to find an object-relational mapper and use it.

Object-relational mapping serves several purposes. One of them is to simplify data access by reimplementing the data access APIs built on .NET.

You need to make a connection between business logic and persistent storage. How you do that depends on how you see your data.