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.

A WCF Service exposes a collection of Endpoints (connections) for communicating with either client applications or other service applications. The mnemonic "ABC" can be used to remember address/binding/contract. Binding specifies what communication protocols are used to access the service, whether security mechanisms are to be used, and the like. WCF includes predefined bindings for most common communication protocols such as SOAP over HTTP, SOAP over TCP, and SOAP over Message Queues, etc. A WCF client connects to a WCF service via an Endpoint. Each service exposes its contract via one or more endpoints. An endpoint has an address (which is a URL specifying where the endpoint can be accessed) and binding properties that specify how the data will be transferred. When a client wants to access the service via an endpoint, it not only needs to know the contract, but it also has to adhere to the binding specified by the endpoint. Thus, both client and server must have compatible endpoints.

The topics in this section show you:

• How to generate a new WCF Plain Service based on Telerik Data Access by using the Service Wizard. Read more
• What is the outcome of the service generation. Read more
• How to: Add Non-Persistent Properties on the Client. Read more
• How to: Update the Generated Service. Read more
• How to: Handle Relationships. Read more
• Error Handling. Read more
• How to: Validate Data. Read more
• Security Considerations. Read more