tweet tweet tweet tweet tweet

Why should I use this framework?


How popular is it?
Real companies building real applications use this framework. Most people who evaluate this framework choose to use it.

There is another popular framework with a download of several megabytes(!!), while yours is only about 100K (the DLL itself is only 40K). What gives?
With this framework you get a framework. Out of the box you'll be able to accomplish 99% of your logging tasks. Yet it isn't bloated with unnecessary complexities. For the 1% of other logging tasks you might have, you can easily extend it.

Is there a book for your framework?
No. That's a good thing. If this framework required a book, one would have to question what they were getting themselves into. It's just a logging framework, after all! It's well-commented, and there's an XML file for help within the Visual Studio IDE.

Am I better off using a framework with a large user community? Who can help me if I have questions?
As a matter of fact, there is a large user base. But there isn't an active board setup specifically for the framework. Why? It isn't needed. But if you do have a question, I'm more than happy to field it.

What do other people say?

What's the bottom line?
This framework succeeds in every way that a good framework should.

  • It's powerful right out of the box.
  • It's easy to use. You won't bang your head against a wall trying to use it.
  • It's simple to extend.

Other .NET tools you may find interesting:
Role-based security made easy


© Copyright 2005 - 2010 - Lorne Brinkman - All Rights Reserved