Application Scenarios (WCF Data Services)
Important
WCF Data Services has been deprecated and will no longer be available for download from the Microsoft Download Center. WCF Data Services supported earlier versions of the Microsoft OData (V1-V3) protocol only and has not been under active development. OData V1-V3 has been superseded by OData V4, which is an industry standard published by OASIS and ratified by ISO. OData V4 is supported through the OData V4 compliant core libraries available at Microsoft.OData.Core. Support documentation is available at OData.Net, and the OData V4 service libraries are available at Microsoft.AspNetCore.OData.
RESTier is the successor to WCF Data Services. RESTier helps you bootstrap a standardized, queryable, HTTP-based REST interface in minutes. Like WCF Data Services before it, Restier provides simple and straightforward ways to shape queries and intercept submissions before and after they hit the database. And like Web API + OData, you still have the flexibility to add your own custom queries and actions with techniques you're already familiar with.
WCF Data Services supports a core set of scenarios for exposing and consuming data as Open Data Protocol (OData) feeds. This topic points you to the topics relevant to these scenarios.
Expose relational data from a database as an OData feed.
Expose arbitrary CLR data classes as an OData feed.
Consume an OData feed in a .NET Framework-based client application.
Consume an OData feed in a Silverlight-based client application.
Consume an OData feed in an AJAX-based client application.
Create an end-to-end data solution that uses OData to transfer data between client and server.
Create a .NET Framework-based client application that consumes an OData feed asynchronously to avoid latency issues on the client.
Expose and consume an OData feed with a binary large object that is accessed and changed as a stream.
Bind OData feeds to controls in a Windows Presentation Framework (WPF) application.
Intercept incoming messages to the data service to perform data validation and role-based filtering of queries.
Create endpoints on a data service to enable custom service behaviors.