.NET Logging Library Specifications
"I cannot describe how satisfied I am by your components! To tell you the truth I started by purchasing the Logging Library but I was so amazed by your products that a couple of days later I also purchased the whole suite!
I totally love all your products and will spread the word for your company!
Keep up the excellent work you are doing!
The .NET Logging Library is the cutting edge of logging. It is more powerful than Log4Net, NLog, or SmartInspect and yet easier to use.
Of course it has all the usual logging capabilities of the other guys including; a wide variety of targets, log levels, filtering, real time monitoring, binary file logging with attachments, and compatibility with log viewers like Chainsaw, Log4View, YALV, LogExpert, and YourLog4Net Viewer.
Say goodbye to editing complex logging XML configuration files. The .NET Logging Library has a GUI configuration editor that can edit external config files and your app.config or web.config files. Setup is literally a minute, versus a half an hour of searching for an appender format and then hoping you didn't make a typo.
We know that you have high maintenance users that cause things to happen in your application that make you scratch your head. That is why the .NET Logging Library can do things like automatically increasing the logging level when an exception occurs. Have a problem user? You can create a logging target for a that specific user by simply re-deploying a new configuration file. If needed, the configuration can be overriden at runtime by your application and then saved. You could easily create an admin page in your application to change the configuration. No other framework does that.
Here are some other differences that will make your life easier. When a junior developer creates an infinite loop and there are thousands of duplicate messages logged, the .NET Logging Library can be configured to ignore duplicate messages. By default, file targets automatically discard older messages after reaching 10,000 entries. 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. No other framework can roll when logging to a database.
The .NET Logging Libary is so easy to use, you can log with a single line of code using the default configuration:
Log.Debug(“This is a test”)
The .NET Logging Library supports all .NET project types including ASP.NET MVC, Webforms, Winforms, WPF, WCF, and Web Services. The logger can be used with any .NET language including VB.NET and C#. Download the full list of features.
|Easy to Use||The .NET Logging Library is implemented as a static class. Logging can be performed with a single line of code. There is no need to wrap an instantiated class in a singleton. However there is also a ConcreteLog class that is ready for mocking with RhinoMocks or Moq.|
|Robust||When asynchronous logging is used, the .NET Logging Library is over three times as fast as Log4Net. The Logger asynchronously processes all messages in a lower priority thread so that it does not affect the performance of your application.|
|Multiple Destinations||Log to multiple simultaneous destinations including the Console, Debug Window, Response, Trace, ASPTrace, the Event Log, multiple databases, email, and files and more. If desired, multithreaded applications can log to a single file. Inherit from BaseTarget to create your own Custom Target.|
|Performance Metrics||The Logging software automatically calculates the difference in milliseconds between the current logged message and the last message that was logged. The Logger also has the ability to track call stack performance. By adding a few logging calls it is easy to see the execution time of sections of code. Simply do a Log.PushMethod() and Log.PopMethod()|
|Run time properties||Unlike the free logging frameworks that are available, the .NET Logging Library has the ability to modify any setting including logging targets, logging levels, and output formatting even while logging is occuring. Other logging frameworks require the external modification of lengthy configuration files. The logging software supports configuration files, including creating default configuration files, but their usage is not required.|
|Log Rolling||The logging tool supports not only discarding old log entries in files, it also supports log rolling of database and event log targets. Log files can be automatically archived by size, time period or maximum log entries.|
|Optimized Database Logging||Tables and optimized stored procedures are automatically created when logging to a database target. All that is needed is the connection string for the database.|
|Object Logging||Log all properties of an object by using reflection. The properties are even sorted in alphabetical order.|
|Ignore Duplicates||The logger can be set to ignore duplicate messages. This can be helpful when a component is throwing the same error multiple times. With this feature, the context of the error is preserved if rolling is enabled.|
|Autolevel Increase||This is an option to enable all logging levels when an error occurs. When a product has been deployed to production and the end user can't remember what they did to get the error, additional logging is turned on automatically.|
|Asynchronous, Buffered and Synchronous Modes||The synchronous mode is a lifesaver when developing console applications. Instead of using Console.Writeline, write out messages using the logger. After development is complete, the logging can be switched to use asynchronous and log to a different destination, such as the event log.|
|Documentation||Industry standard formatted help and an easy to use demo is included.|
|100% Managed Code||100% managed code written in C#. No external dependencies or libraries are required except for the .NET Framework 3.5|
|Royalty Free Distribution||Include with any .NET project royalty free.|
|1 Year Free Upgrades||Purchase today and all upgrades are free for the next year.|
|60 Day Money Back Guarantee||At Kellerman Software, we want you to be totally satisfied with your purchase. Receive a refund within 60 days when ordering from KellermanSoftware.com. Source code versions are non-refundable due to their nature.|
|Lifetime Support||Lifetime E-mail technical support is included.|