Found 356 packages
Package Description
Logging using ILogger is super-useful, but logging directly to a database is sadly lacking. This fixes this, by having a simple SQL logging provider that is easy to setup. You can use appsettings.json or other methods to configure this in your Startup.cs. Be aware that this uses ADO.net and very forcefully creates a table in your database if one does not exist. This only supports SQL Server at this time
Tracing.NET provides basic logging/tracing infrastructure such as an abstracted logger interface ITracer as well as platform specific tracer implementations.
Implementations of the Meadow ILogger interface
Easily add ILogger (non-generic) support logging back into Azure Functions (Isolated Process) for improved DI, better de-coupling from generic types, improved code portability, etc.
Robust logging during .NET Generic Host's HostBuilder configuration stage.
Enables deferred logging against the WebApplicationBuilder during services registration using familiar ILogger abstractions plus dependency injection
Microsoft.Extension.Logging.ILogger implementation for xunit
The package defines logging extensions used by other CodeGator packages. Platforms supported: .NET 6.x or above
TVilaboa forked from nblumhardt/serilog-timings
Extension methods for ILogger to allow easily logging of objects
Package Description
An assembly for extending ILogger activities.
SDK for logging with Archeo with ILogger
Analyze ILoggers at build time and raise warnings on expensive calls.
Unified Logger for Medica applications
A .NET Core logger provider to log directly into a SQL Database.
Console Extensions
zcqlogger
Provides an input implementation for capturing diagnostics data sourced through Microsoft.Extensions.Logging.ILogger