MapVersionedODataRoute or MapVersionedODataRoutes always throws an exception about aspnet-api-versioning HOT 3 CLOSED

Which version of the OData package are you using? I'm guessing you are upgrading a project or creating a new project which is using 6.0.0. There were some pretty significant changes to API and runtime behaviors in 6.0 (see OData 6.x Features for more details). There were a few places where I had to beat the OData APIs into submission, which required nasty, but unavoidable Reflection use. I suspect you are either encountering an incompatible binding redirect from the changes in the APIs or some internal piece of Reflection code is now broken.

Assuming this is your case, then my suggestion would be to use a previous release of the OData package - for now. All of the examples in this project are written against 5.9.1, but I suspect things will work all the way back to at least 5.6 (untested). That should unblock you.

If you can indeed confirm you are using 6.0, then I'll also file a bug that the library is incompatible with 6.0. I haven't dug deep into the changes for 6.0 yet, so I'm not sure how much work it will be; presumably minor. Until I've had some time to look into it, I can't say whether the fix will take a few days or a few weeks. Regardless, I'll start taking a look and get a fix out as soon as possible.

Thanks for reporting the issue. Apologies for the inconvenience.

from aspnet-api-versioning.

Thanks, I appreciate the quick response. I can confirm that I've been using version 6.0.0 of the package. I was planning to try starting fresh with an earlier version of the package to see if that made a difference, but I got hung up in meetings and hadn't had the time to try it yet. Thanks for your help.

from aspnet-api-versioning.

Changing this to an enhancement rather than a bug, since the latest, published API versioning package for OData now indicates that it's not compatible with the OData 6.0.0+ package.

from aspnet-api-versioning.