Microsoft.Extensions.Logging 3.1.5
Logging infrastructure default implementation for Microsoft.Extensions.Logging.
Showing the top 20 packages that depend on Microsoft.Extensions.Logging.
| Packages | Downloads |
|---|---|
|
Serilog.Extensions.Logging
Low-level Serilog provider for Microsoft.Extensions.Logging
|
16 |
|
Volo.Abp.Core
Package Description
|
16 |
|
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
|
16 |
|
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
|
15 |
|
PuppeteerSharp
Headless Browser .NET API
|
14 |
|
Serilog.AspNetCore
Serilog support for ASP.NET Core logging
|
14 |
|
Microsoft.AspNetCore.SignalR.Client.Core
Client for ASP.NET Core SignalR
This package was built from the source code at https://github.com/dotnet/aspnetcore/tree/5ae8106f83d4d23cd0a2d2474c1b15e4d5dfc9eb
|
14 |
|
NLog.Extensions.Logging
NLog provider for Microsoft.Extensions.Logging for usage in .NET Standard libraries and console applicaties.
For ASP.NET Core, use NLog.Web.AspNetCore: https://www.nuget.org/packages/NLog.Web.AspNetCore
|
14 |
|
Ocelot
This project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
13 |
|
BootstrapBlazor
Bootstrap UI components for Blazor and Razor Components
|
13 |
|
OpenTelemetry
OpenTelemetry .NET SDK
|
13 |
|
Volo.Abp.Core
Package Description
|
13 |
|
Microsoft.AspNetCore.Hosting
ASP.NET Core hosting infrastructure and startup logic for web applications.
|
13 |
|
Microsoft.Extensions.Logging.EventLog
Windows Event Log logger provider implementation for Microsoft.Extensions.Logging.
|
13 |
|
Microsoft.AspNetCore.SignalR.Client.Core
Client for ASP.NET Core SignalR
This package was built from the source code at https://github.com/aspnet/AspNetCore/tree/1f050242559e7b90ff6c4ee7f99d92b3a5af5a62
|
13 |
|
Microsoft.AspNetCore.SignalR.Client.Core
Client for ASP.NET Core SignalR
This package was built from the source code at https://github.com/dotnet/aspnetcore/tree/b7a2ec8c7ed6b48857af0a69688a73e8c14fe6cb
|
13 |
.NET Core 3.1
- Microsoft.Extensions.Configuration.Binder (>= 3.1.5)
- Microsoft.Extensions.DependencyInjection (>= 3.1.5)
- Microsoft.Extensions.Logging.Abstractions (>= 3.1.5)
- Microsoft.Extensions.Options (>= 3.1.5)
.NET Standard 2.0
- Microsoft.Extensions.Configuration.Binder (>= 3.1.5)
- Microsoft.Extensions.DependencyInjection (>= 3.1.5)
- Microsoft.Extensions.Logging.Abstractions (>= 3.1.5)
- Microsoft.Extensions.Options (>= 3.1.5)