Comments (7)
.NET 8 support has been released and published. The NuGet packages should be available momentarily.
from aspnet-api-versioning.
Development is in the works. There were a number of changes in the building tooling that had to be resolved. Things are close to being ready. If all goes well, the release should come by week's end. 🤞🏽
from aspnet-api-versioning.
@commonsensesoftware thanks for the follow up. You're correct that we are currently on OData 7. Let me start a new thread.
from aspnet-api-versioning.
will it take care of the stackoverflow?
from aspnet-api-versioning.
@cfauchere Which stackoverflow are you referring to?
from aspnet-api-versioning.
@cfauchere Which stackoverflow are you referring to?
the MapVersionedODataRoutes method leads to stackoverflow after bumping to net8.0
from aspnet-api-versioning.
@cfauchere I'm not sure the exact context here, but MapVersionedODataRoutes
is dead and no longer exists. That was removed from the libraries 2 years ago starting with the official OData 8.0 support. There is no such open issue, nor has it ever been reported for the old Microsoft.AspNetCore.OData.Versioning
library up to 5.1.0
, which only targets .NET Core 3.1 because OData didn't have .NET 5.0 release at the time.
I can't speak for OData's versioning policy or strategy, but it does not align to the .NET version releases. Although it's rare to encounter issues, there is no guarantee that a library that does not target the runtime version will necessarily work. If you target ASP.NET Core 8.0 on .NET 8, then you need a version of such a library targeting .NET 8 to be sure it will work. API Versioning always releases a version that is in alignment with ASP.NET Core and the version of .NET that it builds against. That effort is currently underway. That is what this issue is about.
I can't force people to follow that rule. You can try to make things work with other versions. It might work. It might work and you may never have issues. It is not, however, guaranteed. If that happens, it's unsupported. I have seen issues occur in the wild. Be advised. There be 🐉🐉🐉.
I get the impression you are attempting a rather large update that includes moving to OData 8.x and .NET 8.0. I presume you must have been on OData 7.x or performed some other 🧙🏽♂️🪄 to make things work. If you have questions about migrating or need help, a new discussion might be more appropriate. OData didn't do us any favors in aligning configuration or extension points, but things are more aligned than they used to be. Regardless, there is a significant difference in the setup between OData 7.x to OData 8.x+. The migration guide doesn't cover this situation because the only official version of API Versioning that supports OData 8.0+ is an entirely new package ID and API. The wiki outlines the setup and differences between OData 8.0 vanilla versus with API Versioning, but not in contrast to the old APIs and OData libraries. I'm happy to discuss further to help you move forward.
from aspnet-api-versioning.
Related Issues (20)
- Problem with describing reponse codes in minimal api HOT 3
- Cannot run APIs with different controller names with same ControllerName attribute after migration HOT 6
- Different options in `ApiVersioningOptions.cs` between .NET Framework and .NET Core packages HOT 2
- WithOpenApi() ignore Api versioning readers HOT 4
- Breaking changes when migrating to OData8 + new versioning HOT 10
- odata/$metadata returns 404 when all controllers are decorated with ApiVersionNeutralAttribute HOT 3
- AddVersionedApiExplorer not working in Asp.Versioning HOT 5
- VersionedApiDescriptionProvider does not set the correct SunsetPolicy to ApiDescription instances HOT 1
- Using ApiExplorerSettingsAttribute together with ApiVersionAttribute produces unexpected number of ApiVersionDescriptions HOT 5
- Asp.Net Core WebApi - AWS ECS Cluster Authentication failure HOT 2
- [Versioned Clients][API Notifications] Fails to read new versions when available HOT 2
- Swashbuckle documentation inconsistent with examples HOT 2
- AssumeDefaultVersionWhenUnspecified does not work correctly if ApiVersionNeutral is used in the controller HOT 2
- swagger.json file not found after update HOT 9
- My API is not displaying all the versions. HOT 4
- Improve docs for HeaderApiVersionReader
- Add synonym to `AddMvc` method. HOT 7
- CurrentImplementationApiVersionSelector behaves differently based on whether an operation still exists on latest API version HOT 3
- The error 'code' is not included in the error response when using AddErrorObjects() HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aspnet-api-versioning.