Hi King Wilder,
Your observations are correct. Technically, the old scope approach and the new visual designer achieve one and the same thing – they automate the persistence logic. We are concentrating our efforts on building the new domain model as we think it is more intuitive to work with this new API. Currently, there isn’t anything that you cannot achieve with the new domain model, although we haven’t exposed directly all of the functionality of the IObjectScope. However, internally the OpenAccessContext (the new visual designer approach) internally uses a scope which can be exposed if required. One of the main advantages of using the new domain context is that transaction management is improved and internally handled so that the user does not need to worry about it during development. The new domain model approach tries to automate other tasks which were executed separately with the classic wizards – for example, specifying that you need navigation members for the associations (the “Create one-to-many list” option). What is more, the visual designer makes the control over the model settings and mapping details more convenient with the help of the Model Settings Dialog and Mapping Details Editor. And of course, you do not need to enable the project when you want to include an OpenAccess model. We are also constantly improving our forward mapping features and plan to add other conveniences to the visual designer – such as adding capabilities to easily navigate in large models. The classic scope approach will continue to be fully functional but the new features we add will be mainly noticeable for the visual designer. So, my advice is to use the new approach if you are starting a new project.
I would also like to mention that we will release a dedicated SDK with a rich set of OpenAccess sample applications, guiding you through the development of OpenAccess based projects in all kinds of scenaros. A lot of effort is also put on the Fluent Mapping API and more improvements for the Fetch Optimization API are on our roadmap. Last but not least, we offer support and can help you resolve any problems you encounter on the way to building your applications.
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