See the version list below for details.
dotnet add package Microsoft.Data.Services --version 5.4.0
NuGet\Install-Package Microsoft.Data.Services -Version 5.4.0
<PackageReference Include="Microsoft.Data.Services" Version="5.4.0" />
paket add Microsoft.Data.Services --version 5.4.0
#r "nuget: Microsoft.Data.Services, 5.4.0"
// Install Microsoft.Data.Services as a Cake Addin #addin nuget:?package=Microsoft.Data.Services&version=5.4.0 // Install Microsoft.Data.Services as a Cake Tool #tool nuget:?package=Microsoft.Data.Services&version=5.4.0
Fully-featured server API for responding to OData queries and consuming/producing OData payloads. Supports OData v3. Targets .NET 4.0 or Silverlight 4.0. Localized for CHS, CHT, DEU, ESN, FRA, ITA, JPN, KOR and RUS.
|.NET Framework||net40 net403 net45 net451 net452 net46 net461 net462 net463 net47 net471 net472 net48|
- Microsoft.Data.Services.Client (= 5.4.0)
NuGet packages (12)
Showing the top 5 NuGet packages that depend on Microsoft.Data.Services:
Server API for responding to OData queries and consuming/producing OData payloads based on entity framework version 6.0 or higher Supports OData v3. Targets .NET 4.0.
eXpress Persistent Objects (XPO) is an Object-Relational Mapping (ORM) tool that handles all aspects of database creation and object persistence, allowing you to concentrate on your application's business logic. With XPO, you can build applications that work with multiple database systems without making any changes to your code. More than a dozen of today's most popular database engines are supported, including MS SQL Server, PostgreSQL, MySQL and Oracle.
MongoDB OData provider
This assembly sets up and delivers the OData and WCF webservices.
GitHub repositories (5)
Showing the top 5 popular GitHub repositories that depend on Microsoft.Data.Services:
NuGet Gallery is a package repository that powers https://www.nuget.org. Use this repo for reporting NuGet.org issues.
Hawk protocol implementation for .NET
The Azure Automation PowerShell ISE Add-On makes it easy to author and test your runbooks in your local PowerShell ISE
Client deserialization/serialization hooks
We have a number of investments planned in the “request pipeline” area. In 5.4.0 we have a very big set of hooks for reaching into and modifying data as it is being read from or written to the wire format. These hooks provide extensibility points that enable a number of different scenarios such as modifying wire types, property names, and more.
Instance annotations on atom payloads
As promised in the 5.3.0 release notes, we now support instance annotations on Atom payloads. Instance annotations are an extensibility feature in OData feeds that allow OData requests and responses to be marked up with annotations that target feeds, single entities (entries), properties, etc. We do still have some more work to do in this area, such as the ability to annotate properties.
Client consumption of instance annotations
Also in this release, we have added APIs to the client to enable the reading of instance annotations on the wire. These APIs make use of the new deserialization/serialization pipelines on the client (see above). This API surface includes the ability to indicate which instance annotations the client cares about via the Prefer header. This will streamline the responses from OData services that honor the odata.include-annotations preference.
Simplified transition between Atom and JSON formats
In this release we have bundled a few less-noticeable features that should simplify the transition between the Atom and (the new) JSON format. (See also the bug fixes below on type resolver fixes.)
In addition to the features above, we have included fixes for the following notable bugs:
- Fixes an issue where reading a collection of complex values would fail if the new JSON format was used and a type resolver was not provided
- Fixes an issue where ODataLib was not escaping literal values in IDs and edit links
- Fixes an issue where requesting the service document with application/json;odata=nometadata would fail
- Fixes an issue where using the new JSON format without a type resolver would create issues with derived types
- (Usability bug) Makes it easier to track the current item in ODataLib in many situations
- Fixes an issue where the LINQ provider on the client would produce $filter instead of a key expression for derived types with composite keys
- (Usability bug) Fixes an issue where the inability to set EntityState and ETag values forced people to detach and attach entities for some operations
- Fixes an issue where some headers required a case-sensitive match on the WCF DS client
- Fixes an issue where 304 responses were sending back more headers than appropriate per the HTTP spec
- Fixes an issue where a request for the new JSON format could result in an error that used the Atom format
- Fixes an issue where it was possible to write an annotation value that was invalid according to the term
- Fixes an issue where PATCH requests for OData v1/v2 payloads would return a 500 error rather than 405