OData

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 post OData .NET 8 Preview Release appeared first on OData.

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, The post Deep insert support in OData client appeared first on OData.

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 post Working with media resources in OData – Part 2 appeared first on OData.

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, The post Working with media resources in OData – Part 1 appeared first on OData.

Introduction The latest ASP.NET Core OData supports the following two built-in OData abstract types: Edm.Untyped Collection(Edm.Untyped) 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, The post Enable Un-typed within ASP.NET Core OData appeared first on OData.

Background In OData Web API 7.7.0, 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. The post Deep insert support in OData Web API appeared first on 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, The post Enable CBOR within ASP.NET Core OData appeared first on OData.

Introduction JSON (aka, JavaScript Object Notation), a standard text-based format for representing structured data based on JavaScript object syntax, is the default representation for the OData requests and responses payload, see OData JSON format here. It’s a very popular format and widely used in most scenarios. The post Customize OData payload serialization format within ASP.NET Core OData appeared first on OData.

Good news! OData Web API 7.x now supports bulk operations. Install the most recent version of OData Web API 7.x(v7.6.3) to take advantage of bulk operations. A bulk operation is one that allows you to perform multiple operations (insert, update, delete) on multiple resources (of the same type) and their nested resources (to any level) with a single request. The post Bulk Operations Support in OData Web API appeared first on OData.

Introduction By default, ASP.NET Core OData serializes a single value property as “null”, and a collection value property as an empty array if its value is null as such: { “SingleValueProperty”: null “CollectionValueProperty”: [] } It’s good for most scenarios. However, The post Extension: Omit null value properties in ASP.NET Core OData appeared first on OData.