I am evaling your product. I was working with NHibernate but needed to move to a "released" product that was more established.

However, I am wondering why fields in the Db are created as properties in the Entity class?

For example, I have an akas table which is related (m:1) to a person table. A property named Person is generate to hold an object reference to the related Person entity. But, why is the PersonId field also mapped to a property. It seems to me that this is not needed in the entity class and just clutters up the object?

BOb

Well, you can now do: myOrder.CustomerID = _myCustomerID; and save myOrder without having to have the customer entity loaded into memory. This can save performance. Also for databinding purposes, these properties are required.