Microsoft.OData.Client 6.0.0-beta1

Prefix Reserved
.NET Framework 4.0 This package targets .NET Framework 4.0. The package is compatible with this framework or higher.
This is a prerelease version of Microsoft.OData.Client.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Microsoft.OData.Client --version 6.0.0-beta1                

                    
                

            
NuGet\Install-Package Microsoft.OData.Client -Version 6.0.0-beta1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Microsoft.OData.Client" Version="6.0.0-beta1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add Microsoft.OData.Client --version 6.0.0-beta1                

                    
                

            
#r "nuget: Microsoft.OData.Client, 6.0.0-beta1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install Microsoft.OData.Client as a Cake Addin
#addin nuget:?package=Microsoft.OData.Client&version=6.0.0-beta1&prerelease

// Install Microsoft.OData.Client as a Cake Tool
#tool nuget:?package=Microsoft.OData.Client&version=6.0.0-beta1&prerelease

LINQ-enabled client API for issuing OData queries and consuming OData JSON payloads. Supports OData v4 only. Targets .NET 4.0, and .NET Portable Lib with support for .NET 4.5, SL 5.0, Win Phone 8, and Win 8. Localized for CHS, CHT, DEU, ESN, FRA, ITA, JPN, KOR and RUS.

Product Compatible and additional computed target framework versions.
.NET Framework net40 is compatible.  net403 was computed.  net45 was computed.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

GitHub repositories (14)

Showing the top 5 popular GitHub repositories that depend on Microsoft.OData.Client:

Repository Stars
pnp/PnP
SharePoint / Office 365 Developer Patterns and Practices - Archived older solutions. Please see https://aka.ms/m365pnp for updated guidance
OfficeDev/Microsoft-Teams-Samples
Welcome to the Microsoft Teams samples repository. Here you will find task-focused samples in C#, JavaScript and TypeScript to help you get started with the Microsoft Teams App!
OfficeDev/TrainingContent
Training Content used for developer.microsoft.com/office
OData/WebApi
OData Web API: A server library built upon ODataLib and WebApi
OData/odata.net
ODataLib: Open Data Protocol - .NET Libraries and Frameworks
Version Downloads Last updated
7.5.1 33 9/17/2018
6.16.0 39 4/3/2017
6.11.0 10,733 3/30/2015
6.10.0 4,198 2/6/2015
6.9.0 3,745 12/10/2014
6.8.1 12,161 10/20/2014
6.8.0 1,060 9/23/2014
6.7.0 1,587 8/29/2014
6.6.0 3,541 7/31/2014
6.5.0 2,701 6/30/2014
6.4.0 497 5/30/2014
6.3.0 1,289 4/28/2014
6.2.0 415 4/1/2014
6.1.0 90 3/4/2014
6.0.0 222 1/27/2014
6.0.0-beta1 105 12/9/2013
6.0.0-alpha2 61 11/7/2013
6.0.0-alpha1 72 10/4/2013

This OData V6.0 release includes beta versions of the core .NET libraries described below for implementing OData clients and services that comply with the Committee Specification 02 of the OASIS OData V4 Specification (http://docs.oasis-open.org/odata/odata/v4.0/cs02/part1-protocol/odata-v4.0-cs02-part1-protocol.doc). The libraries support the OData V4 JSON (http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs02/odata-json-format-v4.0-cs02.doc) format; the Atom format is not supported in this release.

What is in the release?

•         Feature Parity
OData V6.0-beta1 release contains all the JSON features in OData V5.6 release that are compatible with OData V4 Protocol, including ODataLib, EdmLib, ODataClient, Spatial. OData V6.0-beta1 supports V4 Protocol only and is not backward compatible with V1-3 Protocol.

•         Enum support
Enum is fully supported for server scenario in JSON. OData client supports CRUD enum property.

•         Singleton support
In this release we get the most common singleton support for server scenario, including defining singleton in EDM, and serializing/deserializing payload in JSON format. UriParser also supports singleton path segment in URI, but it doesn’t support $filter/$select/$expand.

•         Containment support
In this release we get the most common containment support for server scenario, including defining containment in EDM, and serializing/ deserializing payload in JSON format. UriParser also supports containment path segment & $expand in URI, but it doesn’t support $filter/$orderby/$select.

•         Action/Function Support
Action/Function now is now fully supported, except for singleton & containment.

•         V4 compatibility
JSON Reader/Writer, Edmx Reader/Writer and URI Parser have been updated for V4 compatibility, now they all support OData V4 Protocol.

Known Limitations
This beta release of the OData V4 libraries targets functional equivalence with the 5.6.0 release. The OData Client supports the functionality exposed by services written using the server libraries, but there are features required for client interoperability with generic OData V4 services that are not yet supported in this alpha release. Most notably:
• EdmLib doesn't currently support TypeDefinitions, nor referencing external metadata documents, and will fail on services exposing metadata with these constructs
• ODataLib doesn't currently support the presence of singletons, functions, or nested service documents in a service document, and will fail when reading a service document containing these constructs
• ODataLib, EdmLib, and OData Client don't yet support the Date or TimeOfDay datatype, relative IRIs for IDs in JSON, some of the new features of complex types like navigation properties, inheritance, and use in referential constraints, nor some of the new features in singletons and containment.