14.4 OData Web API 7.0 (.NET Core and .NET Classic)
We’re happy to announce the release of ASP.NET Web API OData 7.0 on the NuGet gallery!
ASP.NET Web API OData 7.0 is available in two packages:
- Microsoft.AspNetCore.OData is based on ASP.NET Core 2.0.
- Microsoft.AspNet.OData is based on ASP.NET Web API.
Detail information on Web API OData 7.0 is available here
Get started with ASP.NET Web API OData 7.0 today!
Download this release
You can install or update the NuGet packages for OData Web API v7.0.0 using the Package Manager Console:
PM> Install-Package Microsoft.AspNetCore.OData
or
PM> Install-Package Microsoft.AspNet.OData
What’s in this release?
ASP.NET Core 2.0 support
See main issues from:
-
[ Web API issue #939 ] .NET Core Support.
-
[ Web API issue #772 ] Roadmap for OData WebAPI run on ASP.NET Core.
-
[ Web API issue #229 ] Port ASP.NET Web API OData to ASP.NET 5/MVC 6.
Getting started ASP.NET Core OData from here, get samples from here.
New features
-
[ PR #1497 ] Support
In
operator. -
[ PR #1409 ] Set default to Unqualified-function/acition call and case insensitive.
-
[ PR #1393 ] Set default to enable KeyAsSegment.
-
[ Issue #1503 ] Enable support for Json Batch.
-
[ Issue #1386 ] Use TemplateMatcher for ODataBatchPathMapping.
-
[ Issue #1248 ] Allow recursive complex types in OData model builder.
-
[ Issue #1225 ] Support optional dollar sign.
-
[ Issue #893 ] Support aggregation of Entity Set.
Breaking changes
-
Both Microsoft.AspNetCore.OData and Microsoft.AspNet.OData are using “Microsoft.AspNet.OData” namespace.
-
[ PR #1489 ] Change the OptionalReturn to ReturnNullable in OperationConfiguration.
-
[ PR #1353 ] Change OptionalParameter as Nullable .
Improvements & Fixes:
-
[ Issue #1510 ] move $top & $skip execute as late as possible.
-
[ Issue #1489 ] Return Task<> from method of controller doesn’t pick up odata output formatter (Core).
-
[ Issue #1407 ] Fix the BaseAddressFactory in ODataMediaTypeFormatter .
-
[ Issue #1471 ] Issue in non-odata routing with DataContact & DataMember.
-
[ Issue #1434 ] Add OData-Version into the No-Content response header.
-
[ Issue #1398 ] Expose underlying semantic OData path.
-
[ Issue #1388 ] Make Match as virtual in ODataPathRouteConstraint.
-
[ Issue #1387 ] Move Instance to select all.
-
[ Issue #1313 ] Batch requests are incorrectly routed when ASP.NET Core OData web application has any BasePath.
-
[ Issue #1263 ] Patch nested strucutural resources.
-
[ Issue #1247 ] Fix Spatial post/update problem.
-
[ Issue #1113 ] ODataResourceDeserializer no longer supports null ComplexType values.
-
[ Issue #822 ] Fix for memory leak in EdmLibHelpers.
Questions and feedback
You and your team are warmly welcomed to try out this new version if you are interested in the new features and fixes above. You are also welcomed to contribute your code to OData Web API repository. For any feature request, issue or idea please feel free to reach out to us at GitHub Issues.