slf Wiki & Documentation Rss Feed

Updated Wiki: Home

phsumi — Wed, 02 Dec 2009 15:08:59 GMT

Project Description

SLF is a framework with a simple but ambitious mission: To provide every developer with the means to easily plug in logging functionality into her application.
As such, it aims at two fundamental goals:

Simplicity: SLF allows you to plug in solid logging functionality into your application with literally one line of code, while providing you with an upgrade path to complex logging scenarios at any time.
Flexibility: SLF provides you with a common interface that decouples the logging framework of your choice (e.g. log4net, EntLib, or NLog) from your code. This eliminates dependencies on a given framework, thus allowing you to switch (or even combine!) frameworks at any time. Furthermore, SLF’s modular architecture allows you to plug-in custom logging strategies very easily.

Basically, a façade just provides you with a common interface that decouples the used logging framework from your code:

//ILogger is the facade. Behind the scenes, a framework of your choice is used
ILogger logger = LoggerService.GetLogger();
logger.Info("hello world");

Features

Configurable through code or configuration files (app.config).
Support for named loggers with hierarchical fallback mechanisms.
Support for common logging frameworks such as log4net, NLog and EntLib out of the box.
Silverlight support.
Writing your own pluggable logging strategy is easy.
You can exchange the underlying logging mechanism at any time, even at runtime.
Extensible and modular architecture. Writing your own façade can be as simple as overriding one single method, but you can cover complex scenarios, should you have to.
Robust: In case of invalid configurations or logging instructions, SLF rather outputs debug warnings instead of crashing your application at runtime.
A ton of copy-and-paste ready samples for different use cases.
.NET 2.0 compatible binaries.

External Links

Updated Wiki: Home

phsumi — Wed, 02 Dec 2009 14:53:51 GMT

Simplicity: SLF allows you to plug in solid logging functionality into your application with literally one line of code, while providing you with an upgrade path to complex logging scenarios at any time.
Flexibility: SLF provides you with a common interface that decouples the logging framework of your choice (e.g. log4net, EntLib, or NLog) from your code. This eliminates dependencies on a given framework, thus allowing you to switch (or even combine!) frameworks at any time. Furthermore, SLF’s modular architecture allows you to plug-in custom logging strategies very easily.

Basically, a façade just provides you with a common interface that decouples the used logging framework from your code:

//ILogger is the facade. Behind the scenes, a framework of your choice is used
ILogger logger = LoggerService.GetLogger();
logger.Info("hello world");

Features

Configurable through code or configuration files (app.config).
Support for named loggers with hierarchical fallback mechanisms.
Support for common logging frameworks such as log4net, NLog and EntLib out of the box.
Silverlight support.
Writing your own pluggable logging strategy is easy.
You can exchange the underlying logging mechanism at any time, even at runtime.
Extensible and modular architecture. Writing your own façade can be as simple as overriding one single method, but you can cover complex scenarios, should you have to.
Robust: In case of invalid configurations or logging instructions, SLF rather outputs debug warnings instead of crashing your application at runtime.
A ton of copy-and-paste ready samples for different use cases.
.NET 2.0 compatible binaries.

External Links

The Art of Logging @ CodeProject
SLF Introduction

Updated Wiki: Home

ColinEber — Wed, 02 Dec 2009 14:09:30 GMT

Simplicity: SLF allows you to plug in solid logging functionality into your application with literally one line of code, while providing you with an upgrade path to complex logging scenarios at any time.
Flexibility: SLF provides you with a common interface that decouples the logging framework of your choice (e.g. log4net, EntLib, or NLog) from your code. This eliminates dependencies on a given framework, thus allowing you to switch (or even combine!) frameworks at any time. Furthermore, SLF’s modular architecture allows you to plug-in custom logging strategies very easily.

Basically, a façade just provides you with a common interface that decouples the used logging framework from your code:

//ILogger is the facade. Behind the scenes, a framework of your choice is used
ILogger logger = LoggerService.GetLogger();
logger.Info("hello world");

Features

Configurable through code or configuration files (app.config).
Support for named loggers with hierarchical fallback mechanisms.
Support for common logging frameworks such as log4net, NLog and EntLib out of the box.
Silverlight support.
Writing your own pluggable logging strategy is easy.
You can exchange the underlying logging mechanism at any time, even at runtime.
Extensible and modular architecture. Writing your own façade can be as simple as overriding one single method, but you can cover complex scenarios, should you have to.
Robust: In case of invalid configurations or logging instructions, SLF rather outputs debug warnings instead of crashing your application at runtime.
A ton of copy-and-paste ready samples for different use cases.
.NET 2.0 compatible binaries.

Updated Wiki: Home

phsumi — Wed, 02 Dec 2009 13:35:04 GMT

Simplicity: SLF allows you to plug in solid logging functionality into your application with literally one line of code, while providing you with an upgrade path to complex logging scenarios at any time.
Flexibility: SLF provides you with a common interface that decouples the logging framework of your choice (e.g. log4net, EntLib, or NLog) from your code. This eliminates dependencies on a given framework, thus allowing you to switch (or even combine!) frameworks at any time. Furthermore, SLF’s modular architecture allows you to plug-in custom logging strategies very easily.

Basically, a façade just provides you with a common interface that decouples the used logging framework from your code:

//ILogger is the facade. Behind the scenes, a framework of your choice is used
ILogger logger = LoggerService.GetLogger();
logger.Info("hello world");

Features

Configurable through code or configuration files (app.config).
Support for named loggers with hierarchical fallback mechanisms.
Support for common logging frameworks such as log4net out of the box.
Silverlight support.
Writing your own pluggable logging strategy is easy.
You can exchange the underlying logging mechanism at any time, even at runtime.
Extensible and modular architecture. Writing your own façade can be as simple as overriding one single method, but you can cover complex scenarios, should you have to.
Robust: In case of invalid configurations or logging instructions, SLF rather outputs debug warnings instead of crashing your application at runtime.
A ton of copy-and-paste ready samples for different use cases.
.NET 2.0 compatible binaries.

Updated Wiki: Home

phsumi — Wed, 02 Dec 2009 11:25:34 GMT

Simplicity: SLF allows you to plug in solid logging functionality into your application with literally one line of code, while providing you with an upgrade path to complex logging scenarios at any time.
Flexibility: SLF provides you with a common interface that decouples the logging framework of your choice (e.g. log4net, EntLib, or NLog) from your code. This eliminates dependencies on a given framework, thus allowing you to switch (or even combine!) frameworks at any time. Furthermore, SLF’s modular architecture allows you to plug-in custom logging strategies very easily.

Basically, a façade just provides you with a common interface that decouples the used logging framework from your code:

//ILogger is the facade. Behind the scenes, a framework of your choice is used
ILogger logger = LoggerService.GetLogger();
logger.Info("hello world");

Features

Configurable through code or configuration files (app.config).
Support for named loggers with hierarchical fallback mechanisms.
Support for common logging frameworks such as log4net out of the box.
Silverlight support.
Writing your own pluggable logging strategy is easy.
You can exchange the underlying logging mechanism at any time, even at runtime.
Extensible and modular architecture. Writing your own façade can be as simple as overriding one single method, but you can cover complex scenarios, should you have to.
Robust: In case of invalid configurations or logging instructions, SLF rather outputs debug warnings instead of crashing your application at runtime.
A ton of copy-and-paste ready samples for different use cases.
.NET 2.0 compatible binaries.

Updated Wiki: Home

phsumi — Tue, 25 Aug 2009 07:05:55 GMT

Project Description
This logging façade provides you with a common interface that decouples the logging framework of your choice from your code, thus minimizing dependencies on said facility.

Basically, a façade just provides you with a common interface that decouples the used logging framework from your code:

//ILogger is the facade. Behind the scenes,
//a framework of your choice is used
ILogger logger = LoggerService.GetLogger();
logger.Info("hello world");

The idea of a logging façade isn’t exactly new, but we thought we’d share this one with you for a few reasons:

Simplicity is key: You can enable logging for your application with a single line of code.
Support for a great number of logging frameworks out of the box (and writing your own façade is easy, too!)
The core library has no dependencies on other libraries at all.
SLF is not part of another project (completely standalone), and there is no license attached to it. Do with it whatever you want.

However, while "Simple" is a key concept in SLF, it does not mean that you will loose flexibility:

Programmatic or declarative configuration of loggers and used logging frameworks.
Support for named loggers with fallback mechanisms.
Flexibility is key - SLF sports and extensible and modular architecture. Every module can be replaced at runtime.
Writing your own façade is as simple as overriding one single method, but you can cover complex scenarios, should you have to.
You can easily log to multiple logging frameworks at the same time without having to change any of your code.

Please be aware that the API is becoming stable, but there may be minor changes in the very near future.

Updated Wiki: Home

phsumi — Fri, 22 May 2009 20:08:35 GMT

//ILogger is the facade. Behind the scenes,
//a framework of your choice is used
ILogger logger = LoggerService.Logger;
logger.Log("hello world");

The idea of a logging façade isn’t exactly new, but we thought we’d share this one with you for a few reasons:

It is dead easy to use.
It provides quite a few overloads when it comes to logging.
The core library has no dependencies on other libraries at all.
There are two façades (separate DLLs) that log through the Enterprise Library Logging block or the BitFactory logger. And hopefully more to come!
Writing your own façade is as simple as overriding one single method.
It’s not part of another project (completely standalone), and there is no license attached to it. Do with it whatever you want.
It is dead easy to use.

The sources here provide the contents of the introductory tutorial that was first published at http://www.hardcodet.net/2009/04/simple-logging-facade (apart from an additional DelegateLogger). The library works well, but please note that the API might change in the very near future once we get started here.