Open Source Logging Tools in C#
|log4net is a tool to help the programmer output log statements to a variety of output targets. log4net is a port of the excellent log4j framework to the .NET runtime.
* Support for multiple frameworks
* Output to multiple logging targets
* Hierarchical logging architecture
* XML Configuration
* Dynamic Configuration
* Logging Context
* Proven architecture
* Modular and extensible design
* High performance with flexibility
Go To log4net
|The C# Logger is designed after the log4j project by apache. It is a logging tool that can be used to write events such as debug, info, warn and error messages to the Windows event log.
Go To CSharp Logger
|Extensible .NET Logger written in C#, with advanced message queuing allowing for complete asynchronous use
Go To CSharp Dot Net Logger
|Logger.NET is a logging framework which enables you to include code which contains logging information
Go To Logger.NET
|LogThis C# logging framework is a drop-in logging tool module for .Net applications.
Go To LogThis
|NLog is a simple logging library similar in concepts to log4net, designed with simplicity and flexibility in mind. NLog project is hosted at sourceforge.net.
.NET, .NET Compact Framework and Mono 1.0 support
very easy to configure, both with a config file and programmatically
easy to use - interface is identical to Console.WriteLine
Go To NLog
|TraceTool is C# trace Framework and a viewer.
The viewer can also display real time traces from Event Log messages, OutputDebugString, and text files (like unix tail-f)
The framework can also be used as an appender for logNet,
system.Trace and Microsoft Enterprise Instrumentation Framework (EIF).
You can send simple traces, tree oriented traces, objects, dump and call stack.
Finally, the framework is also available for Java and Delphi.
Go To TraceTool
|Common.Logging is a library to introduce a simple abstraction to allow you to select a specific logging implementation at runtime. There are a variety of logging implementations for .NET currently in use, log4net, Enterprise Library Logging, NLog, to name the most popular. They do not share a common interface and therefore impose a particular logging implementation on the users of your library. Common.Logging solves this problem.
Go To Common.Logging
|LMAH (Error Logging Modules and Handlers) is an application-wide error logging facility that is completely pluggable. It can be dynamically added to a running ASP.NET web application, or even all ASP.NET web applications on a machine, without any need for re-compilation or re-deployment.
Once ELMAH has been dropped into a running web application and configured appropriately, you get the following facilities without changing a single line of your code:
* Logging of nearly all unhandled exceptions.
* A web page to remotely view the entire log of recoded exceptions.
* A web page to remotely view the full details of any one logged exception.
* In many cases, you can review the original yellow screen of death that ASP.NET generated for a given exception, even with customErrors mode turned off.
* An e-mail notification of each error at the time it occurs.
* An RSS feed of the last 15 errors from the log.
Go To Elmah