OData

Create and consume RESTful APIs in a simple and standard way

Support for fetching nested paths in OData Web API

Background OData services use nested paths to access properties or entities related to a resource. For example, if you want to access orders of a given customer, you would use a request path like: http://localhost:8080/Customers/1/Orders Microsoft.AspNetCore.OData 7.x provides two main approaches for handling such requests: convention ...
Comments are closed.0 0

Build formatter extensions in ASP.NET Core OData 8 and hooks in ODataConnectedService

Introduction In this post, I will create formatter extensions in an OData web service and request/response hooks in an OData client application to generate/consume ETag control information. ETag (aka entity tag), one of OData control information that may be applied to an entity or collection in response, can be used in a subsequent request to...

Feedback usabilla icon