Microsoft.OData.Core 6.2.0

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Microsoft.OData.Core --version 6.2.0
NuGet\Install-Package Microsoft.OData.Core -Version 6.2.0
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.Core" Version="6.2.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add Microsoft.OData.Core --version 6.2.0
#r "nuget: Microsoft.OData.Core, 6.2.0"
#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.Core as a Cake Addin
#addin nuget:?package=Microsoft.OData.Core&version=6.2.0

// Install Microsoft.OData.Core as a Cake Tool
#tool nuget:?package=Microsoft.OData.Core&version=6.2.0

Classes to serialize, deserialize and validate OData JSON payloads. Supports OData v4 only. Enables construction of OData producers and consumers. Targets .NET Portable Lib with support for .NET 4.0, SL 5.0, Win Phone 8, and Win 8. Localized for CHS, CHT, DEU, ESN, FRA, ITA, JPN, KOR and RUS.
OData .NET library is open source at https://odata.codeplex.com/

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

GitHub repositories (29)

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

Repository Stars
smartstore/SmartStoreNET
Open Source ASP.NET MVC Enterprise eCommerce Shopping Cart Solution
Squidex/squidex
Headless CMS and Content Managment Hub
pnp/PnP
SharePoint / Office 365 Developer Patterns and Practices - Archived older solutions. Please see https://aka.ms/m365pnp for updated guidance
grandnode/grandnode
Open source, headless, multi-tenant eCommerce platform built with .NET Core, MongoDB, AWS DocumentDB, Azure CosmosDB, Vue.js.
OfficeDev/TrainingContent
Training Content used for developer.microsoft.com/office
Version Downloads Last updated
7.5.1 6 9/17/2018
6.16.0 46 4/3/2017
6.11.0 27,611 3/30/2015
6.10.0 21,087 2/6/2015
6.9.0 17,766 12/10/2014
6.8.1 22,373 10/20/2014
6.8.0 5,212 9/23/2014
6.7.0 4,509 8/29/2014
6.6.0 4,860 7/31/2014
6.5.0 21,866 6/30/2014
6.4.0 10,725 5/30/2014
6.3.0 1,606 4/28/2014
6.2.0 437 4/1/2014
6.1.0 115 3/4/2014
6.0.0 376 1/27/2014
6.0.0-beta1 202 12/9/2013
6.0.0-alpha2 63 11/7/2013
6.0.0-alpha1 59 10/4/2013

What is in the release:

Bug fixes:

•   Fixed a bug for parsing $it in UriParser

•   Improved the JSON serialization performance for unindented format

New Features:

•   ODataLib & EdmLib now supports complex type inheritance and open complex type.

•   ODataLib & EdmLib now supports open collection property in entity and complex type.

•   OData Client now supports property level change tracking for PATCH.
DataServiceCollection now supports property level change tracking. By default only changed properties will be included in the payload for update (PATCH) operations, unless you explicitly use SaveChangesOptions.ReplaceOnUpdate when calling SaveChanges(). The entity level change tracking behavior is not changed in DataServiceCollection.

•   OData Client supports using different type/property name than the name in metadata by OrginalNameAttribute
Previously the type and property name in proxy class must be same as metadata. Now you can use over-write the type/property name by using OriginalNameAttribute:

   [global::Microsoft.OData.Client.OriginalNameAttribute("product")]    
   public partial class Product
   {
       // Using camel case in metadata
       [global::Microsoft.OData.Client.OriginalNameAttribute("name")]
       // Using Pascal case in proxy class
       public string Name
       {
           get;
           set;
       }
   }

•   ODataLib support generating ServiceDocument from EdmModel directly by extension method GenerateServiceDocument().

Known Issues:

•   Type casting for complex type in $filter and $select is not supported.

•   Reading individual property of derived complex type directly by OData Client is not supported.