Create and consume RESTful APIs in a simple and standard way
March 27, 2014Mar 27, 201403/27/14WCF 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.
March 21, 2014Mar 21, 201403/21/14Hi 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.
March 21, 2014Mar 21, 201403/21/14Hi 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.
March 20, 2014Mar 20, 201403/20/14We are very excited to announce the availability of nightly builds on MyGet for ASP.NET Web API 2.2 for OData v4.0 along with OData Client Code Generator for writing OData v4 clients. The Web API 2.2 release is particularly noteworthy as it is the first Web API release with support for OData v4 with selected highly demanded features.
March 18, 2014Mar 18, 201403/18/14Enumeration 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,
March 12, 2014Mar 12, 201403/12/14Are 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,
March 12, 2014Mar 12, 201403/12/14Before 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”
March 11, 2014Mar 11, 201403/11/14Edited on July 09, 2014 by updating “Add OData Client Proxy File” for V2.0.0 and adding “Appendix” part. Please refer to “OData Client Code Generator 2.0.0 release” for V2.0.0 release notes
Edited on Apr 29, 2014 by adding “Upgrade the Project Dependencies to the Most Recent Version”
March 5, 2014Mar 5, 201403/5/14Ever had a special entity where there can be only one of its kind, but bothered by having to define a one-element entity set for it? Ever wanted to request a special entity but bothered by needing to find out its key first?
