Resources
Data Access has been discontinued. Please refer to this page for more information.

Service Generation Outcome

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.

The Service Wizard allows you to generate ATOM Service based on Telerik Data Access. This topic discusses the changes that the wizard will make to your project.

References

The wizard adds references to:

  • System.ServiceModel.dll
  • System.Runtime.Serialization.dll
  • System.ServiceModel.Web.dll
  • Telerik.OpenAccess.dll
  • Telerik.OpenAccess.35.Extensions.dll
  • <Your Telerik Data Access Model Project>

Generated Files

When ATOM Service is generated, the wizard will automatically create several additional files and will add them to the Output project.

  • Assemblers.cs - contains implementation of the Assembler pattern that translates DTO types into Entity types and vice versa. In the case of DTO to Entity types the generated assemblers CAN (not enabled by default) set navigation properties for references and collections.
  • Converter.cs - contains converters from one value format to another. In this particular case it is KeyUtility that is responsible for conversion of ObjectKey values to string values.
  • DynamicLinq.cs - extension methods that enable definition of IQuerable<T> calls using string predicates instead of lambda expressions.
  • EntitiesModelService.svc - markup files for the generated service. This is the hosting svc file.

  • EntitiesModelService.svc.cs - contains the implementation of the service contract. The implementation of the operations is delegated to the mini-services defined in Services.cs. Provides specific formatters and syndication feeds/links.

    EntitiesModelService.svc.vb file in VB projects, use the Show All Files command from the Solution Explorer toolbar.

  • IEntitiesModelService.cs - this is the service contract interface.

  • Repositories.cs - contains implementation of the Repository pattern that enables access to the data shaped by your decision in step 3 of the wizard. Provides CRUD operations interface to the database.
  • Services.cs - contains separate services that operated on a single entity. These services are not exposed at service level.
  • Transport.cs - contains DTO types definitions that are transported between the client and the server in order to encapsulate the data access layer entities from the outside world.