cool-webapi
serilog-ui
Our great sponsors
| cool-webapi | serilog-ui | |
|---|---|---|
| 6 | 1 | |
| 50 | 193 | |
| - | 2.6% | |
| 1.3 | 7.2 | |
| about 1 year ago | 5 days 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.
cool-webapi
-
What every ASP.NET Core Web API project needs - Part 6 - IServiceCollection Extension
So far I have added and configured several packages to the cool-webapi project and in the future articles I will add more packages and configuration and the Startup class will become a large class.
-
What every ASP.NET Core Web API project needs - Part 5 - Polly
You can find the source code for this walkthrough on Github.
-
What every ASP.NET Core Web API project needs - Part 4 - Error Message Reusability and Localization
Open Startup.cs class and follwing codes:
-
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.
serilog-ui
-
What every ASP.NET Core Web API project needs - Part 1 - Serilog
If you're using SQL Server, PostgreSQL or MongoDB sinks, I have developed a small log viewer for small projects. It helps a lot, especially in the production environment and you don't need to query the database to view logs.
What are some alternatives?
api-guidelines - Microsoft REST API Guidelines
Serilog - Simple .NET logging with fully-structured events
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
serilog-sinks-console - Write log events to System.Console as text or JSON, with ANSI theme support
serilog-sinks-mssqlserver - A Serilog sink that writes events to Microsoft SQL Server and Azure SQL
serilog-sinks-elasticsearch - A Serilog sink that writes events to Elasticsearch
ASP.NET Identity
Serilog.Sinks.WinForms - Print Serilog logs from anywhere in you application into textbox or datagridview. windows forms
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.
serilog-settings-configuration - A Serilog configuration provider that reads from Microsoft.Extensions.Configuration