Chris Martinez

@Gigabyte0x1337 thank you for confirming. Preview 3 is just around the corner. Some folks asked so if you still need .NET Core 3.1, it will be included as a target....

The `6.0` release is fully signed and published. I don't think there is any more to add here. I've opened up a [discussion](../discussions/862) for the release if there are more...

This is hard to tell. API Versioning doesn't officially support OData on .NET 5 because OData doesn't officially support it either. OData has some pre-releases, but I don't have capacity...

Did you ever solve this? There are a number of test cases and the OpenAPI/Swagger example demonstrate the use of numerous OData functions. You custom convention _shouldn't_ be affecting that,...

This thread appears to have ended. `6.0` has been released and contains a ton of fixes and new features, including support for OData 8x. and .NET 6.0. In all likelihood,...

@davidebriscese Thanks for the repro; it really helps. It took less time that I thought; I missed something obvious. I noticed that both of you are trying to use _part_...

@HuntJason it simply not possible - currently. OData 8.0+ is not yet supported. There's a much longer discussion about this in #677. Unfortunately, the OData team has pulled the rug...

@HuntJason indeed, it's unfortunate. I know some of the contacts, but discussions and feedback seem to go in one ear and out the other. I guess _some_ communication channel is...

@sjd2021 as has now be flushed out (I _think_), I suspect you are using only part of OData. While it is possible for that to work from a pure API...

@sjd2021 you got it. Essentially, `ODataQueryOptions` is no longer seen as _special_ and the type is treated as a normal _model_. The default behavior is to treat such models as...