John Gathogo

@josundt Can you describe what you're trying to do? Are you swapping the serializer with System.Text.Json

@josundt I took a look at your repro. The reason your service is not behaving as expected is because you're missing something at the section where you add the endpoint...

@josundt Here's what I meant when I said that we don't use System.Text.Json. When `AddOData()` is invoked, the custom OData input and output formatters are added to the very top...

@andrewschmidt-a Thank you for reporting the issue. There was a change that was released in the not-so-distant past that introduced a `BaseEntityType` class that the proxy classes inherit from. That...

@KaterynaKateryna That you for reporting this issue. Unfortunately I'm unable to reproduce it. Find [here](https://github.com/gathogojr/ODataWebApiIssue2594Repro/tree/master/ODataWebApiIssue2594Repro.V7x) my attempt at reproducing it and paging works just fine. I referenced Microsoft.AspNetCore.OData 7.4.1 specifically....

@KaterynaKateryna The additional information and context helps. Let me try and see if I can identify the problem

@KaterynaKateryna The `PagedResponse` type you're using is not from the OData library so I really don't have any knowledge of the implementation. Below is how you'd you'd accomplish the same...

@KaterynaKateryna A lot of things could have changed between 5.x and 7.x. Breaking changes are usually included in major releases. You may need to debug through the implementation of `PagedResponse`...

To verify the workaround applied in OData WebApi repo https://github.com/OData/WebApi/blob/03bf03855f1c86f0138fc7ade01c02a3ad4b772a/src/Microsoft.AspNet.OData.Shared/Formatter/Serialization/ODataResourceSetSerializer.cs#L201

> Can we get some benchmarks for this change I added some comparison results for before and after and @habbes also run some benchmarks and shared the data in a...