aspnet-api-versioning
Versioning.NET
Our great sponsors
- SonarQube - Static code analysis for 29 languages.
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
- InfluxDB - Access the most powerful time series database as a service
| aspnet-api-versioning | Versioning.NET | |
|---|---|---|
| 10 | 3 | |
| 2,727 | 16 | |
| 1.0% | - | |
| 9.2 | 0.0 | |
| about 1 month ago | about 1 month ago | |
| C# | C# | |
| MIT License | MIT License |
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.
aspnet-api-versioning
-
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.
Versioning.NET
-
Make Your .NET Startup Code More Modular with StartupOrchestration.NET
Plus, if you're looking for a way to automate versioning in your .NET projects, check out my Versioning.NET repository, which is also used to version StartupOrchestration.NET.
- Automatic .NET Versioning Tool
What are some alternatives?
Nerdbank.GitVersioning - Stamp your assemblies, packages and more with a unique version generated from a single, simple version.json file and include git commit IDs for non-official builds.
api-guidelines - Microsoft REST API Guidelines
Evolve - Database migration tool for .NET and .NET Core projects. Inspired by Flyway.
GitVersion - From git log to SemVer in no time
dotnet-setversion - .NET Core CLI tool to update the version information in .NET Core *.csproj files
CleanArchitecture - Clean Architecture Solution Template for .NET 7
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
marionette - Marionette is a test automation framework based on image and text recognition for .NET.
CommandLineUtils - Command line parsing and utilities for .NET
liz - liz (ˈlɪz) is a tool to extract license-information from your project/solution aimed on a fast and correct process. Whether it's via a dotnet-CLI-Tool, Cake-Addin or Nuke-Addon
Verlite - Automatically version projects via semantic git tags with a focus on being lite, optimized for continuous delivery.
copy-paster - Copy-paste-driven development made easy.