Versioning.NET
aspnet-api-versioning
| Versioning.NET | aspnet-api-versioning | |
|---|---|---|
| 3 | 12 | |
| 19 | 2,991 | |
| - | 1.2% | |
| 3.6 | 8.7 | |
| about 1 year ago | 4 days 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.
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.
- Question about app versioning...
- Automatic .NET Versioning Tool
aspnet-api-versioning
-
Web API Versioning - 'apiVersion' constraint
Here is a code example
- Best way to version a CQRS-oriented REST api
- How do you handle API versioning? And naming.
- Is this a common way to version REST apis
-
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.
-
Entity Changes and API Versioning - Looking for best practice
https://github.com/dotnet/aspnet-api-versioning/tree/master/samples/aspnetcore/BasicSample/Controllers something like this
-
API version control (route name error)
Could you not achieve what you want by using ASP.NET API versioning - there's a by namespace example here
-
.NET Core — API Versioning
A lista completa pode ser vista aqui: https://github.com/microsoft/aspnet-api-versioning/wiki/Version-Format
-
Web API in 5 Hours (2021)
You don't have to use attributes. You can use conventions. See here.
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.
CleanArchitecture - Clean Architecture Solution Template for ASP.NET Core
dotnet-setversion - .NET Core CLI tool to update the version information in .NET Core *.csproj files
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
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
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
GitVersion - From git log to SemVer in no time
ApiVersioningSwagger - Api Versioning Swagger example
marionette - Marionette is a test automation framework based on image and text recognition for .NET.
bitplatform - Build all of your apps using what you already know and love ❤️