Chris Martinez

I'd be curious if you ever had a working repro. I've tried multiple combinations and I simply cannot make anything work. I even tried completely removing API Versioning from the...

Gotcha. Glad you got something working, even if it wasn't what you were hoping for.

Looks like there is a solution to this issue. `6.0` has been officially released and contains all of the fixes, including the `LockRecursionException` problem. The `6.0` release may be a...

I'll have to go back and research this. I found at least one edge case where the logic was wrong and fixed it. That _might_ have caused some expected behavioral...

Circling back around to this issue. I can confirm that this is indeed a regression in `4.2.0`. It appears to have been fixed in `5.0.0`. I updated your repro to...

@pwdst , @jocf `6.0` is now available in [preview](../../releases/tag/v6.0.0-preview.2) and changes some internal routing mechanics, which I believe will address the routing issues. `404`, `405`, and `415` should be reported...

`6.0` is officially released. If that resolves the issue for you, then I'd like to close this out. I'm still fighting publishing issues with code signing `5.1`, which also contains...

This issue has been fixed in `6.0` so I'm going to close this out. I'm still waiting on MS to unblock me on publishing the `5.1` packages and, at this...

Interesting. I'll have a look. The strange thing is the current source doesn't show anything on [line 198](../blob/main/src/AspNetCore/OData/src/Asp.Versioning.OData.ApiExplorer/ApiExplorer/ODataApiDescriptionProvider.cs#L198). The repro will definitely help. Thanks

Doh! Hmm... looks like `apiVersion` is somehow coming up `null`. That shouldn't happen. Defending against `null` is easy, but I suspect there is a little more to the issue.