[Discussion] Future Direction of WCF Data Services

Mike PizzoMarch 27, 2014Mar 27, 201403/27/14

WCF Data Services
Microsoft initially released WCF Data Services as an easy way to implement an OData service over queryable data sources. This made it very easy to expose a model backed by the Entity Framework as an OData Service, and included a data provider model for plugging in other types of queryable data sources.

[Announcement] ODataLib 6.1.0 release

Yi Ding - MSFTMarch 21, 2014Mar 21, 201403/21/14

Hi all,
As our commitment in rolling out new functionality in the OData V4 protocol continuously, we are excited to announce that OData Core Libraries 6.1 has been released to NuGet.  This release contains four packages, Core, EDM, Spatial and the .Net client.

[Announcement] OData core libraries now support OData v4

Yi Ding - MSFTMarch 21, 2014Mar 21, 201403/21/14

Hi all,
We are tremendously excited to announce that we have released version 6.0.0 of the OData core libraries to NuGet on Jan 27th. This release is particularly noteworthy as it is the first production-ready releasewith support for OData v4, the newest version of the OData protocol.

[Tutorial & Sample] Use Enumeration types in OData

Tian OuyangMarch 18, 2014Mar 18, 201403/18/14

Enumeration is a very common data type in various data models. Enumeration types are useful means to represent data that needs to support certain programmatic options (such as the ability to detect one or more options are selected). OData v4 now supports Enumeration types,

[Tutorial & Sample] Using Parameter Alias to simplify the OData URL

tjf_azureMarch 12, 2014Mar 12, 201403/12/14

Are you suffering from typing complex parameter values in URL? Or even make it worse you need to type it more than once?
To solve this problem, now Microsoft.OData.Core.dll 6.0 supports parameter alias in request URL， such as: ~/People?$filter=LastName eq @name and contains(Description,

[Tutorial & Sample] Containment is Coming with OData V4

Liang Wang [MSFT]March 12, 2014Mar 12, 201403/12/14

Before OData V4, every entity set must be accessed from top-level even it is in a containment relationship with other set. For example, assume a schema where Order Lines (Type: “OrderLine”, EntitySet: “OrderLines”) live within Orders (Type: “Order”, EntitySet: “Orders”). Then, Orders have an “id”