Actually there isn’t such a comparison available in one place. The features are scattered all over the documentation. Here I will provide a brief comparison of the two contexts.
Both IObjectScope and Entity Diagrams context offer access to the collection of mapped entity objects. You can use LINQ to query your data easily using both. By using both contexts you can also add, update, delete and refresh objects and save or discard changes; monitor changes; execute stored procedures; retrieve objects by the unique key identifying them. With the IObjectScope you can access the transaction properties but you need to manage the life cycle of the transaction execution (making sure a transaction is started whether it is set automatically or not). With the new Entity Diagrams context you can call SaveChanges and let the transaction management be transparent to your business logic. The IObjectScope also provides the ability to track changes by implementing custom logic for the tracking events. Besides, you can use OQL and execute SQL statements. However, the same functionality and even more flexibility can be achieved with LINQ. If you need to expose the functionality of the IOBjectScope with the new context you can define a class which extends the Entity Diagrams context class and use the protected method which returns an IObjectScope.
As to your first question, by the sound of it, you are forward mapping a model and trying to understand the underlying column names. Currently with the forward mapping wizard you can see the generated DB column name. In case you use the reverse mapping visual designer, the mapping details editor also hints at the DB column and property match. In the forward mapping scenario you need to be careful with the naming conventions we use by default. If you do not specify a field for a property you want to have in your entity, the name recorded in the database will be one that may not always be very meaningful to you. To avoid the confusion you can specify fields which are wrapped by the properties. Thus the naming rules can benefit from the name of the field.
Do not hesitate to contact us for further questions.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items