The .NET Logging Library is the cutting edge of logging.  It is more powerful than Log4Net, NLog, or SmartInspect and yet easier to use.  It also has intelligent defaults. 

The .NET Logging Library can log to many different targets including, AspTrace, Databases, Files, CSV Files, HTML Files, XML Files, Event Log, and much more.  The .NET Logging Library can perform real time logging to Chainsaw, Log4View or a custom TCP/IP logger.  It has the ability to log to a binary file with binary attachments.  When an exception is logged, the logging level can automatically be increased for more information.  When there are thousands of duplicate messages, the .NET Logging Library can ignore duplicate messages. 

The .NET Logging Library is so easy to use, you can log with a single line of code using the default configuration:
Log.Debug(“This is a test”)

We have made the configuration for logging super easy.  Configuration can be set with runtime properties, an external XML file or inside the app.config or web.config.  There is a powerful configuration editor that pulls the logging section out of the app.config file and saves it back in, retaining non-related settings. 

The .NET Logging Library has intelligent defaults.  If it detects that it is in a console application, WinForm application, or WPF application, it will automatically log to the console, and a file.  The file will automatically roll after 10,000 entries.  If the logger detects it is in an ASP.NET application, it will log to Response.Write.  When logging to a database, it will automatically create the logging table and the corresponding stored procedure to log to the database and roll database entries.