Namespace Dapplo.Log

Abstract implementation for ILogger, which safes some time. In general you will only need to implement Write (without exception) as: 1) WriteLine in calls Write after appending a newline. 2) WriteLine with Exception calls WriteLine with the template/parameters and again with the Exception.ToString()

The logic for the mapping of loggers

A simple wrapper for some information which is passed to the logger

The extensions for making logging easy and flexible

This is to specify global settings for the Log "framework"

This defines the "source" (origin) for log statements, it should have a Type or a identifier (string) so it's clear where the log entries come from. In general this should be instanciated with the default constructor without arguments, which takes care of initiating it. For normal .NET 4.5 this uses the Stack to find the type which called the constructor. For other platforms this uses the CallerFilePath, which supplies the source-file.

The extensions for making logging easy and flexible

An null logger, doesn't log anything! This can be used to shut-up certain LogSources

This is the interface used for internal logging. The idea is that you can implement a small wrapper for you favorite logger which implements this interface. Assign it to the HttpExtensionsGlobals.Logger and Dapplo.HttpExtensions will start logger with your class. A TraceLogger implementation is supplied, so you can see some output while your project is in development.

Interface for the LoggerConfiguration

Log level for the log, default(LogLevel) gives None which doesn't log anything LogLevels.None is actually checked internally, before IsLogLevelEnabled.