Chris Martinez

@BlackRider97, @PranjaliSoni thanks for the updated information; this is useful. This was a very deep investigation. Lucky you, you're the winner of two bugs! The first bug is in API...

I just wanted to circle back around and provide a quick update on this issue. After a **lot** of researching, I can confirm that this is indeed a bug and...

The [Preview 2](../releases/tags/v6.0.0-preview.2) release available and you can pick up the changes from the new package [Asp.Versioning.Mvc](https://www.nuget.org/packages/Asp.Versioning.Mvc). While I could make the change in `5.1`, I've decided not to because...

`6.0` has been officially released. It contains the official, final release of the changes discussed throughout this thread. You discovered a pretty big hole in the implementation, but a lot...

Apologies for the delayed follow-up. Did you ever figure this out? From your repro, there isn't anything glaring. I notice there are some custom Swashbuckle annotations. I'm not sure what,...

This definitely _could_ be an issue, but I believe it has been solved. Starting in `6.0`, the assembly name will start with `V__` so that you can easily tell which...

I also forgot to mention that, unfortunately, a better exception message cannot be provided because that comes from Swashbuckle, not API Versioning or ASP.NET Core.

`6.0` _Preview 3_ is now available (and with support for .NET Core 3.1 😉 ). I believe this issue is now fixed, but you'll want to double-check. I vague remember...

`6.0` has been officially released. Can you double-check whether this issue still exists? I suspect it doesn't. If it's resolved, then let's close it out. If it isn't, then I'll...

The repro was helpful. ### Issue 1 I'm not sure if you'll 😆 or 😭 , but OData _strikes_ again! The first issue is that the controller is wrong. It...