OData
Create and consume RESTful APIs in a simple and standard way
Latest posts
Announcing OData .NET 8 Release Candidate 1
OData .NET 8.0 RC1 is now available, bringing numerous significant improvements to the following libraries: This is the final release candidate before the official launch of these libraries, scheduled for August 12th. Most of the planned features and changes are included in this release candidate and are ready for you to explore. In addition to the changes listed in these documents: This release includes the following updates: Some of these updates are breaking changes. Updates in Version 8.0.0-rc.1 We invite you ...
Microsoft.AspNetCore.OData 9 Preview Release
We are excited to announce the forthcoming major release of Microsoft.AspNetCore.OData, scheduled for June. In preparation for this significant update, we have made preview versions of the library available to gather early feedback from our community. The following preview release is now available on NuGet: Key Update The primary change in this release is the update of the OData core libraries dependencies to the recently released OData Core 8.0.0-preview versions. To review the breaking changes and updates made in the OData Core libraries, which we have incorporated into this release, please check t...
OData .NET 8 Preview Release
We would like to announce that we are planning a new major release of OData .NET core libraries in June. Ahead of this release, we have released preview versions of the libraries to get some early feedback from the community. Specifically, the following preview releases are now available on NuGet: It has been almost 8 years since the last major release of OData .NET core libraries. This release presents an opportunity for us to modernize our stack, address some technical debt and take better advantage of investments in .NET. To make adoption and upgrading to the new version smooth, we have op...
Deep insert support in OData client
In the Deep insert support in OData webapi blog post, we demonstrated how to add deep insert capabilities to an OData service. In this blog post, we demonstrate how to add deep insert capabilities in OData client. In the following sections, we implement a client app. Create a Console application Install required packages In our client application, we are going to use the library that offers APIs for building deep insert requests and consuming deep insert responses. Run the following command on the Visual Studio Package Manager Console to install the nuget package...
Working with media resources in OData – Part 2
In Part 1 of this blog post, we demonstrated how to implement an OData service that serves media resources. In Part 2, we look at how to implement a client app that interacts with the OData binary large object (BLOB) feed to both retrieve and post binary data along with the metadata for the media resource. The OData BLOB feed created in Part 1 supported the following functionality: The service also exposed a single media link entry (MLE) named that is linked to a media resource (MR). In the following sections, we implement a client app to interact with that BLOB feed. Create a Con...
Working with media resources in OData – Part 1
OData enables you to define data feeds that serve binary large object (BLOB) data. In OData lingo, this binary data is referred to as a media resource. A media resource (MR) is an unstructured piece of data or stream, e.g., a document, image, or video. It is requested from the data service separately from the entry in the feed to which it belongs, called a media link entry. A media link entry (MLE) is a special type of entry which links to an MR and includes additional metadata about it. Typical metadata that an MLE may maintain about the related MR include description, file name, file size, dimensions, date uplo...
Enable Un-typed within ASP.NET Core OData
Introduction The latest ASP.NET Core OData supports the following two built-in OData abstract types: Developers can use them to advertise a property in OData metadata schema (aka, Edm model) so that such property is declared with a particular name present, but there is no type associated to describe the structure of the property's values. Here's an example: Where, Data is called single value untyped property, meanwhile Infos is called collection value untyped property. Since they are untyped, in other words, there's no type limitation for the property value, developers can use any kind of val...
Deep insert support in OData Web API
Background In , we added support for deep insert. In deep insert, we create an object and its related items or link existing items in a single request. This blog post is a continuation of Bulk Operations Support in OData Web API. In that blog post, we explained how to use and classes. We will not repeat that in this blog post. Bulk update and deep insert share the same and classes. In the following sections, we will cover how deep insert is implemented in and the things that the developer needs to do to use it in their OData service. Controller For the controller action to handle deep insert, the...
Enable CBOR within ASP.NET Core OData
Introduction CBOR, which stands for Concise Binary Object Representation, is a data format whose design goals include the possibility of extremely small code size, small message size, and extensibility without the need for version negotiation (from cbor.io). CBOR is based on the wildly successful JSON (aka, JavaScript Object Notation) data model, and is a binary data representation of JSON. Here's an example of a simple JSON value in plain text and binary representation. OData library, by default, uses the plain text JSON representation for OData requests and response data serialization (writing) and dese...