Domain Class Mapping - Overview
This article is relevant to entity models that utilize the deprecated Visual Studio integration of Telerik Data Access. The current documentation of the Data Access framework is available here.
When you have a model first scenario, you build the domain classes first and then derive the database schema from the domain model. Telerik Data Access supports two ways of mapping newly added domain classes to tables. The first approach is to use default mapping. When you use default mapping, Telerik Data Access takes care of the property to column mapping. In other words, when you have a Model First Scenario and you use the default mapping functionality, Telerik Data Access will take care for the columns and table naming. On the other side, the explicit mapping gives you more control over the columns\table naming. This section discusses both approaches: