You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrading to Microsoft.AspNet.OData v7 will break the ApiVersioning code (specifically 'MapVersionedODataRoutes') with the error "The type 'ODataRoute' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Web.OData, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'."
The text was updated successfully, but these errors were encountered:
Honestly, I've been a little laissez-faire with restricting the versions used by dependent packages. I plan to rectify that for all packages in all future releases. The OData libraries, in particular, are notorious for introducing significant breaking changes. This makes it difficult for both me and the customers. I simply don't have capacity to support 3+ flavors of the OData libraries.
If you require an official package, then you are stuck with OData 6.x and API versioning 2.x. For the latest and greatest, you can use API versioning 3.0, which is currently in beta, but targets OData 7.0. I'm working to get out Beta 2 as quickly as possible. The main changes in OData support for API versioning 3.0 is support OData 7.0, which is largely only namespace changes in OData. There aren't a bunch of changes or new features. Despite the beta label, you should expect the API versioning package to be stable and working with the same quality as 2.x.
I hope that clarifies things and unblocks you for the time being. I'll use this issue to track clipping dependent package references to their major versions. Thanks.
Upgrading to Microsoft.AspNet.OData v7 will break the ApiVersioning code (specifically 'MapVersionedODataRoutes') with the error "The type 'ODataRoute' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Web.OData, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'."
The text was updated successfully, but these errors were encountered: