Today, I also paid attention to the discussion of .NET ORM http://community.9cbs.net/expert/topic/3517/3517657.xml?temp =.8789636 is more confused with the problem of the business layer and the performance layer map below .NET, I have left the Laosan Comrade, I don't know if I have a reply, I will leave a message, I have been going to be a testistic project under. Net below. I am most confused is the mapping problem of the business layer to the performance layer. After reading the << object-oriented data control binding solution >>, in addition to data binding, the serialization of data is also a problem, and your solution is bound to the architecture provided by the performance layer. Together.
I consider making an Assemble Layer Framework between the business layer and the performance layer, load the OO business object as the DataSet table structure, which (1) can utilize the DataSet and the control binding mechanism and the automatic serialization mechanism of Dataset (2 The object of the business layer has a lot of reference relationships. When assemble, it can only return to the most needed objects to the interface rather than all references. (3) The upper developer habits DataSet's processing, there is no need to use other implementations of the five flowers .
I don't know what you have, add a middle layer, and lose a little less. I don't know that MS provides ObjectSpace. Is there a similar Assemble Layer solution. Or ObjectSpace's persistent Object base class object provides serialization and tie Type mechanism
