| uid | title | author | description | ms.author | ms.date | ms.assetid | msc.legacyurl | msc.type |
|---|---|---|---|---|---|---|---|---|
web-api/overview/releases/whats-new-in-aspnet-web-api-odata-53 |
What's New in ASP.NET Web API OData 5.3 | Microsoft Docs |
rick-anderson |
This topic describes the new features and bug fixes introduced in ASP.NET Web API OData 5.3 and provides links to downloads and documentation. |
riande |
09/16/2014 |
e39eaa25-83ff-41dc-869d-3818d59a88ae |
/web-api/overview/releases/whats-new-in-aspnet-web-api-odata-53 |
authoredcontent |
by Microsoft
This topic describes what's new for ASP.NET Web API OData 5.3.
- Download
- Documentation
- OData Core Libraries
- New Features
- Known Issues and Breaking Changes
- Bug Fixes
- ASP.NET Web API OData 5.3.1
The runtime features are released as NuGet packages on the NuGet gallery. You can install or update to the released NuGet packages by using the NuGet Package Manager Console:
[!code-consoleMain]
You can find tutorials and other documentation about ASP.NET Web API OData at the ASP.NET web site.
For OData v4, Web API now uses ODataLib version 6.5.0
You can use the $levels query option in $expand queries. For example:
[!code-consoleMain]
This query is equivalent to:
[!code-consoleMain]
An open type is a structured type that contains dynamic properties, in addition to any properties that are declared in the type definition. Open types let you add flexibility to your data models. For more information, see xxxx.
Previously, a dynamic property had to be a single value. In 5.3, dynamic properties can have collection values. For example, in the following JSON payload, the Emails property is a dynamic property and is of collection of string type:
[!code-consoleMain]
Now complex types can inherit from a base type. For example, an OData service could define the following complex types:
[!code-csharpMain]
Here is the EDM for this example:
[!code-xmlMain]
For more information, see OData Complex Type Inheritance Sample.
This section describes known issues and breaking changes in the ASP.NET Web API OData 5.3.
Issue: Using nested $expand with $levels=max results in an incorrect expansion depth.
For example, given the following request:
[!code-consoleMain]
If MaxExpansionDepth is 5, this query would result in an expansion depth of 6.
This release also includes several bug fixes and minor feature updates.
In this release we made a bug fix to some of the AllowedFunctions enums. This release doesn't have any other bug fixes or new features.