WCF Data Services: Overview

WCF Data Services: Overview

WCF Data Services (formerly known as "ADO.NET Data Services") is a component of the .NET Framework that enables you to create services that use the Open Data Protocol (OData) to expose and consume data over the Web or intranet by using the semantics of representational state transfer (REST). OData exposes data as resources that are addressable by URIs. Data is accessed and changed by using standard HTTP verbs of GET, PUT, POST, and DELETE. OData uses the entity-relationship conventions of the Entity Data Model to expose resources as sets of entities that are related by associations.

WCF Data Services uses the OData protocol for addressing and updating resources. In this way, you can access these services from any client that supports OData. OData enables you to request and write data to resources by using well-known transfer formats: JavaScript Object Notation (JSON), a text-based data exchange format used extensively in AJAX application, and Atom, a set of standards for exchanging and updating data as XML.

WCF Data Services can expose data that originates from various sources as OData feeds. Visual Studio tools make it easier for you to create an OData-based service by using an ADO.NET Entity Framework data model. You can also create OData feeds based on common language runtime (CLR) classes and even late-bound or un-typed data.

WCF Data Services also provides client libraries to access OData feeds from applications created in Visual Studio that target the following platforms:

These client libraries provide an object-based programming model when you access an OData feed in your application. 

For a comprehensive list of available content that discusses WCF Data Services and OData, see the topic WCF Data Services Content Survey.

Other Languages

This article is also available in the following languages:

Leave a Comment
  • Please add 1 and 7 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
  • Ed Price - MSFT edited Revision 11. Comment: Removing White Space. Made "Other Languages" a Header 1 (was H3).

  • Ed Price - MSFT edited Revision 7. Comment: We're not going to add "(en-US)" to the titles because of various difficulties. Please continue to add the tag though!

  • Horizon_Net edited Revision 6. Comment: Added language tags

  • Horizon_Net edited Revision 5. Comment: added link to the german version of this article

  • Nevin Janzen edited Revision 4. Comment: Tags Edit

  • Glenn Gailey [MSFT] edited Revision 3. Comment: WCF in the product name should not be linked

Page 1 of 1 (6 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • Glenn Gailey [MSFT] edited Revision 3. Comment: WCF in the product name should not be linked

  • wcf both speed and very reliable data as a distributor

  • Nevin Janzen edited Revision 4. Comment: Tags Edit

  • Horizon_Net edited Revision 5. Comment: added link to the german version of this article

  • Horizon_Net edited Revision 6. Comment: Added language tags

  • Ed Price - MSFT edited Revision 7. Comment: We're not going to add "(en-US)" to the titles because of various difficulties. Please continue to add the tag though!

  • Ed Price - MSFT edited Revision 11. Comment: Removing White Space. Made "Other Languages" a Header 1 (was H3).

Page 1 of 1 (7 items)