AspNetCoreOData | NET Core OData : A server library built upon ODataLib

by OData C# Version: 8.1.2 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | AspNetCoreOData Summary

AspNetCoreOData is a C# library. AspNetCoreOData has no bugs, it has no vulnerabilities and it has low support. However AspNetCoreOData has a Non-SPDX License. You can download it from GitHub.

Be noted: Switch to use "main" as default branch. 1/6/2022. This is the official ASP.NET Core OData repository. ASP.NET Core OData is a server side library built upon ODataLib and ASP.NET Core.

Support

Quality

Security

License

Reuse

Support

AspNetCoreOData has a low active ecosystem.

It has 348 star(s) with 130 fork(s). There are 29 watchers for this library.

It had no major release in the last 12 months.

There are 338 open issues and 301 have been closed. On average issues are closed in 104 days. There are 16 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of AspNetCoreOData is 8.1.2

Quality

AspNetCoreOData has 0 bugs and 0 code smells.

Security

AspNetCoreOData has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

AspNetCoreOData code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

AspNetCoreOData has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

AspNetCoreOData releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 14321 lines of code, 0 functions and 1002 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of AspNetCoreOData

Get all kandi verified functions for this library.

AspNetCoreOData Key Features

No Key Features are available at this moment for AspNetCoreOData.

AspNetCoreOData Examples and Code Snippets

No Code Snippets are available at this moment for AspNetCoreOData.

Community Discussions

Trending Discussions on AspNetCoreOData

IHttpContextAccessor.HttpContext is null after execution falls out of the UseODataBatching middleware and causing NullReferenceExp in IdentityServer

Odata Global PageSize

$Metadata url returns 404 with Microsoft.AspNetCore.OData 8.0.0-rc2

Odata filtering in expanded property does not work

QUESTION

IHttpContextAccessor.HttpContext is null after execution falls out of the UseODataBatching middleware and causing NullReferenceExp in IdentityServer

Asked 2022-Mar-04 at 04:31

I have a simple .NET6 OData API with the default configuration with Batch enabled. The API is configured with IdentityServer from the default VS template.

Program.cs

...

ANSWER

Answered 2022-Mar-04 at 04:31

I ended up adding a middleware that repopulates the IHttpContextAccessor manually.

Source https://stackoverflow.com/questions/71338662

QUESTION

Odata Global PageSize

Asked 2022-Feb-06 at 14:38

Can someone please explain why my EnableQueryAttribute filter is not firing when the client query does not include the Count=True in their query? My entire dataset is returned.

...

ANSWER

Answered 2022-Feb-06 at 14:38

Have you tried deliberately setting the property in the constructor? This has the added benefit of still allowing you to override the default page size at each endpoint.

Source https://stackoverflow.com/questions/70791713

QUESTION

$Metadata url returns 404 with Microsoft.AspNetCore.OData 8.0.0-rc2

Asked 2021-May-12 at 19:46

After updating to Microsoft.AspNetCore.OData from 7.5.8 to 8.0.0-rc2 the ~/odata/$metadata url is not working anymore, it just returns 404 - Not found.

Before I file a bug, am I doing the configuration wrong?

I followed this blog and the somewhat updated documentation in the Git repo.

Here is my original Startup.cs for 7.5.8:

...

ANSWER

Answered 2021-May-11 at 22:31

I found the solution:

I had to change the sdk in the csproj file from Microsoft.NET.Sdk.Worker to Microsoft.NET.Sdk.Web.

(Basically the project is a .NET 5 SDK-style Windows Service / BackgroundWorker with an Asp.Net Core API included.)

It seems this was not an issue with earlier versions before 8.*

Source https://stackoverflow.com/questions/67482878

QUESTION

Odata filtering in expanded property does not work

Asked 2021-Feb-19 at 14:57

We have created a .NET Core API which uses Odata to filter, select, and expand the data. The data is stored in a Microsoft SQL Server database and retrieved through EntityFramework Core (code first). We use Linq projection so the Odata filter is applied directly to the query, but this gives an error in the following situation:

When retrieving a list of results, e.g. authors expanded with books, everything works fine. It gives an error when filtering inside the expanded books e.g.: https://localhost:44316/odata/authors?$expand=Books($filter=Id eq 1)

...

ANSWER

Answered 2021-Feb-18 at 20:42

Well, it is common mistake when working with Expresion Tree. You cannot use ToDto in that way. LINQ translator has to see Expression Tree but not compiled lambda.

There are two libraries, that I know, and which can help you to achieve this result:

https://github.com/hazzik/DelegateDecompiler

https://github.com/axelheer/nein-linq

Then you have to rewrite your helper methods (using DelegateDecompiler):

Source https://stackoverflow.com/questions/66257708

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install AspNetCoreOData

You can download it from GitHub.

Support

ODataRoutingSample: ASP.NET Core OData sample project in this repo. ASP.NET OData 8.0 Preview for .NET 5: A blog introducing the project. Our docs folder: Our current documentation.

Find more information at: