ApiVersioningSwagger
Api Versioning Swagger example (by njunior1980)
aspnet-api-versioning
Provides a set of libraries which add service API versioning to ASP.NET Web API, OData with ASP.NET Web API, and ASP.NET Core. (by dotnet)
Our great sponsors
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
- SonarLint - Clean code begins in your IDE with SonarLint
- InfluxDB - Access the most powerful time series database as a service
| ApiVersioningSwagger | aspnet-api-versioning | |
|---|---|---|
| 1 | 10 | |
| 2 | 2,727 | |
| - | 1.0% | |
| 0.0 | 9.2 | |
| 5 months ago | about 1 month ago | |
| C# | C# | |
| - | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ApiVersioningSwagger
Posts with mentions or reviews of ApiVersioningSwagger.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-22.
aspnet-api-versioning
Posts with mentions or reviews of aspnet-api-versioning.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-04-12.
-
Angular, ASP.NET core web api, and DTOs
- The DTOs on the server should generally not change without warning. A deprecation cycle should ideally be in place so consumers can keep up over time and front end development doesn't have to be lock-step with the services the consume. Ideally some period of time between service v1 being deprecated and service v2 being required to allow consumers to react ( in this case, you're the consumer, so be kind to yourself ). Deets: https://github.com/dotnet/aspnet-api-versioning
-
8 quick tips to improve your .NET API
This API versioning can be parameterized with some options, including the default version or even how the versioning will be done, whether by URL, header or media type. For more details, you can access the official documentation.
-
.NET Core — API Versioning
A lista completa pode ser vista aqui: https://github.com/microsoft/aspnet-api-versioning/wiki/Version-Format
-
What every ASP.NET Core Web API project needs - Part 2 - API versioning and Swagger
Check out the official API versioning Github repository to find out more information.
What are some alternatives?
When comparing ApiVersioningSwagger and aspnet-api-versioning you can also consider the following projects:
api-guidelines - Microsoft REST API Guidelines
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
CleanArchitecture - Clean Architecture Solution Template for .NET 7
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
ASP.NET Boilerplate - ASP.NET Boilerplate - Web Application Framework
Versioning.NET - A dotnet tool that automatically increments versions in csproj files based on git commit hints.