aspnet-api-versioning
cool-webapi
Our great sponsors
| aspnet-api-versioning | cool-webapi | |
|---|---|---|
| 10 | 6 | |
| 2,660 | 32 | |
| 3.0% | - | |
| 9.4 | 0.7 | |
| 11 days ago | over 1 year ago | |
| C# | C# | |
| 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.
cool-webapi
-
What every ASP.NET Core Web API project needs - Part 3 - Exception handling middleware
In the previous article, I wrote about API versioning and how to add Swagger to the sample project with support of API versioning. In this article, I show how to add custom middleware to handle exceptions globally and create a custom response when an error occurred.
-
What every ASP.NET Core Web API project needs - Part 2 - API versioning and Swagger
Open the cool-webpi project and Install Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer package
-
What every ASP.NET Core Web API project needs - Part 1 - Serilog
Source code for this walkthrough could found on the Github.
What are some alternatives?
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
serilog-ui - Simple Serilog log viewer UI for several sinks.
ApiVersioningSwagger - Api Versioning Swagger example
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
ASP.NET Boilerplate - ASP.NET Boilerplate - Web Application Framework
ASP.NET Identity
serilog-sinks-mssqlserver - A Serilog sink that writes events to Microsoft SQL Server and Azure SQL
Serilog - Simple .NET logging with fully-structured events
Versioning.NET - A dotnet tool that automatically increments versions in csproj files based on git commit hints.