|Advisory: https://github.com/advisories/GHSA-mv2r-q4g5-j8q5||Severity: high|
See the version list below for details.
dotnet add package Microsoft.Data.OData --version 5.5.0
NuGet\Install-Package Microsoft.Data.OData -Version 5.5.0
<PackageReference Include="Microsoft.Data.OData" Version="5.5.0" />
paket add Microsoft.Data.OData --version 5.5.0
#r "nuget: Microsoft.Data.OData, 5.5.0"
// Install Microsoft.Data.OData as a Cake Addin #addin nuget:?package=Microsoft.Data.OData&version=5.5.0 // Install Microsoft.Data.OData as a Cake Tool #tool nuget:?package=Microsoft.Data.OData&version=5.5.0
Classes to serialize, deserialize and validate OData payloads. Enables construction of OData producers and consumers.
Targets .NET 4.0 or Silverlight 4.0.
Localized for CHS, CHT, DEU, ESN, FRA, ITA, JPN, KOR and RUS.
|Product||Versions 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.|
|Silverlight||sl4 is compatible. sl5 was computed.|
GitHub repositories (109)
Showing the top 5 popular GitHub repositories that depend on Microsoft.Data.OData:
Store securely encrypted backups in the cloud!
Experience, Learn and Code the latest breakthrough innovations with Microsoft AI
Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform.
The open source diagnostics platform for the web
SharePoint / Office 365 Developer Patterns and Practices - Archived older solutions. Please see https://aka.ms/m365pnp for updated guidance
With this release, the URI Parser in ODataLib is nearly complete. The URI Parser is now capable of parsing nearly every URI supported by the current OData stacks at Microsoft (Web API and WCF Data Services).
Public Data Source Providers
We frequently get requests to make the data source providers in WCF Data Services public. Making these providers public enables a number of profoundly interesting scenarios ranging from changing the behavior of an existing provider to adding support for features we don't currently support. The work completed in this release will allow limited modifications of the existing providers. We plan to enable more scenarios here in the future.
We constantly strive to improve performance and reliability with every release. In this release, we have increased performance by double digit percentages for service authors that want to respond with JSON but are not able to (or don't want to) provide a data model to ODataLib.
Improved Developer Experience
In this release we have caught up with some missing IntelliSense guidance and we are uploading symbols and source to SymbolSource.org. We will upload symbols for many of our past releases as well.
In addition to the features above, we have included fixes for the following notable bugs:
- Fixes an issue where the reflection provider would not work properly if the generic parameter provided to DataService<T> was an interface
- Fixes an issue where some system headers were not being set when a client called BuildingRequest
- Fixes an issue where setting InstanceContextMode to Single on DataService would result in cache result being returned for subsequent requests
- Fixes an issue where ODataLib would sometimes allow null to be written whether or not the expected type was nullable
- Fixes a regression in 5.4 where ODataLib started writing unnecessary type information in certain instances
- Fixes an issue where the WCF DS client would sometimes not dispose the response if the response had no content
- Improves a number of errors and error messages