LighterLog 1.3.0

LightLog

A lightweight logger created with dependency injection in mind. It is done for the most part.

Loggers

There are different kinds of loggers that come with this library. Here they are and what they do:

1. The basic logger Logger: This logger has the most flexibility as it is single-threaded. The AsyncLogger was recently merged with this Logger type so both synchronous and asynchronous methods are available depending on the required use case. An available option with this logger is the provided pre and post log events so users of the library can have their own things happen right before and right after a log happens. This type also comes with a static Shared property for a quick-start to logging with a single instance. This property can be reassigned.
2. The toggle logger ToggleLogger: Backed by any kind of other ILogger, comes with an internal boolean state that determines whether or not a log will happen. Has a backing ILogger that all methods are delegated to. To get this, use the "UseForDebugging" extension method available to all ILogger implementations. This one can be good for debugging. One example of using this logger for debugging is using the DEBUG preprocessor flag to enable logging, otherwise leave disabled. The only loss in performance at that point is a boolean check that is guaranteed to be false. If the boolean is guaranteed to be false, so is the return type. That means the JIT will most likely optimize it so it doesn't affect anything.
3. The global logger found statically as Shared in the Logger class is a partial extension to make a single logger widely accessible for quick starting. This is lazy and will only be initialized on the first retrieval. This comes with all capabilities of Logger.

Planned additions

• A thread-independent logger that logs in its own separate thread using a blocking collection, concurrent queue and cancellation tokens.

NuGet

The package can be found on NuGet here