Models mapped with the Visual Designer
tool (Domain Models
) and models mapped with Fluent Mapping
(Fluent Models) offer the same persistence capability and change tracking. From the point of a project consuming a model, both Domain and Fluent Models act in the same manner.
That being said each model type has specific features not present in the other. Here is a list of key points regarding the two model types
- Uses the Visual Designer tool to define or modify the mapping of the model.
- Code for the persistent classes, the model context class is generated automatically after the initial creating of the model. After that it is re-generated automatically when saving the model in order to reflect changes in the mapping.
- Offers visual wizards for updating/creating the model from a database or vice versa.
- The Service Wizard can generate various web services based on the model.
- Allows for greater customization of the model. This is due to the fact that code is auto-generated only once - when creating the model from an existing database.
- The mapping is defined manually by code in C# or VB.Net using the Fluent API.
- Allows for the usage of Artificial Types - types defined at runtime.
You could also check out the Getting Started section
of our documentation as it shows examples of using both Domain and Fluent models.
I hope this helps. Do not hesitate to contact us again in case you have additional questions or need help.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map