This project has moved and is read-only. For the latest updates, please go here.

CuttingEdge.Logging v1.3

Rating: No reviews yet
Downloads: 314
Change Set: 54755
Released: Aug 25, 2010
Updated: Nov 3, 2010 by dot_NET_Junkie
Dev status: Stable Help Icon

Recommended Download

Application CuttingEdge.Logging Runtime Library v1.3.zip
application, 422K, uploaded Sep 2, 2010 - 163 downloads

Other Available Downloads

Source Code CuttingEdge.Logging Source Code v1.3.zip
source code, 663K, uploaded Sep 2, 2010 - 77 downloads
Documentation CuttingEdge.Logging.chm
documentation, 392K, uploaded Aug 25, 2010 - 42 downloads
Application Common.Logging v2.0 Adapter for CuttingEdge.Logging v1.3.zip
application, 6K, uploaded Sep 2, 2010 - 32 downloads

Release Notes

CuttingEdge.Logging is a library that helps the programmer output log statements to a variety of output targets in .NET applications. The design is based on the .NET 2.0 Provider Model. This means the library uses the same configuration and extensibility model and .NET developers should very fast feel very familiar with CuttingEdge.Logging.

This release has some great usability improvements. First of all the new XmlFileLoggingProvider has been added to allow writing information to the file system in an XML format. Besides this, all loggers now allow to be created using code-based configuration. This means that the you can use the library without using the static Logger class and without having to configure it in the application configuration file. The code-based configuration can be used by instantiating the providers using one of the non-default constructors. Next, the AspNetSqlLoggingProvider is now independent of the ASP.NET Membership security system. Last but not least, all loggers now support the logging of exceptions with multiple inner exceptions, which is will be a very common scenario from .NET 4.0 and up.

Bug fixes
  • The MailLoggingProvider nog disposes SmtpClient instances when running inside .NET 4.0 or higher. Work item 6133. Note that CuttingEdge.Logging is still compatible with .NET 2.0.

Code changes
  • The AspNetExceptionLoggingModule will now hook up to the AppDomain.UnhandledException event to log any fatal exceptions that might take the AppDomain down.
  • Added a base class FileLoggingProviderBase that acts as base class for logging to a file.
  • A new XmlFileLoggingProvider has been added. Work item 6006.
  • AspNetSqlLoggingProvider now uses HttpContext.User.Identity.Name and IPrincipal.Identity.Name for retrieving the current logged-on user name, instead of using the System.Web.Security.Membership. This makes the usage of this logger more flexible and improves performance. Work item 6092.
  • The library is now able to handle exceptions with multiple inner exceptions. Work item 4028. When an Exception contains a public 'InnerExceptions' property (such as both the .NET 4.0 System.AggregateException and CuttingEdge.Logging.CompositeException contain), the framework will use this property instead of the InnerException property. The SqlLoggingProvider and AspNetSqlLoggingProvider will store all inner exceptions in the database. The MailLoggingProvider and WindowsEventLogLoggingProvider will display information about the inner exceptions in their output by using the exception's ToString() method.
  • The API of the provided logging provider classes is now changed in such a way that code-based configuration becomes possible. This means that the logging providers now support optional constructors that allow a provider to be completely initialized, without the need to call Initialize(string, NameValueCollection). Work item 5143.
  • AspNetSqlLoggingProvider now uses HttpContext.User.Identity.Name and IPrincipal.Identity.Name for retrieving the current logged-on user name, instead of using the System.Web.Security.Membership. This makes the usage of this logger more flexible and improves performance. Work item 6092.

Reviews for this release

No reviews yet for this release.