Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Logging an Exception

Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

The latest Enterprise Library information can be found at the Enterprise Library site.

A frequently required exception-handling task is to log the information associated with the exception. The Exception Handling Application Block, in conjunction with the Logging Application Block, lets you log formatted exception information in locations specified in the configuration file. For example, client applications typically log application information in the event log, while a server component of an e-commerce application may log exceptions in a database.

You want to log an exception that occurred in one of the application layers before any other exception handling occurs. Your application has code in its catch blocks similar to the following.


Ff647499.note(en-us,PandP.10).gifNote:
The code does not include the FormatException and Logger.Log methods. These methods represent typical application code to create a formatted exception message and write it to a log destination.


catch(SomeException e)
{
  string formattedInfo = FormatException(e);
  Logger.Log(e);

  throw e;
}

Designate the logging handler as the first handler in your policy's exception handling chain. The Exception Handling Application Block includes the logging handler.

For an extended example of how to log an exception, see the QuickStart walkthrough, Walkthrough: Logging an Exception.

To use the logging handler, you must configure the application exception policies and the Logging Application Block. You must then modify your application to use the appropriate exception handling policy.

To configure the application exception policies

  1. Use the configuration tools to create an exception handling policy for your application layer. For more information, see Entering Configuration Information.
  2. Specify the exception types to be processed and logged.
  3. Add the logging handler as the first handler for each exception type.
  4. Configure the logging handler:
    1. Enter the event ID.
    2. Enter the logging categories.
    3. Select the severity.
    4. Enter the title of the log entry.
    5. Select the formatter type name.
    6. Enter the priority.
  5. Add any additional exception handlers to be invoked after the logging handler.

To configure the Logging Application Block

  1. Add the Logging Application Block to your application configuration (adding a logging handler will automatically add the Logging Application Block to your application configuration). For more information, see Adding Application Code in the documentation for The Logging Application Block.
  2. Configure the Logging Application Block.

Modify your application code to execute the new policy when an exception occurs. The following code demonstrates how to do this. Substitute the name "Logging Policy" with the name of your own policy.

try
{
  // Run code.
}
catch(Exception ex)
{
  bool rethrow = ExceptionPolicy.HandleException(ex, "Logging Policy");
  if (rethrow)
    throw;
}

Consider the following information when you configure the application block to use a logging handler:

  • Exceptions can be logged any time during processing; they do not have to be logged at the beginning of the event handling sequence. For example, you can log an exception after it is wrapped or replaced.
  • The Exception Handling Application Block provides a logging exception handler that depends on the Logging Application Block. You can also incorporate custom logging functionality into your own exception handler to use instead of the Logging Application Block.
  • The preceding code example uses a single generic handler for all managed exceptions (these are exceptions derived from the System.Exception class. Your own application could have other catch statements that call the HandleException method with different policies or that do not use the Exception Handling Application Block. The code in this example uses the policy name "Logging Policy" to emphasize its behavior. Generally, a policy name reflects the application layer or component that uses it, instead of its function. For example, a policy used by the data access layer would be named "Data Access Layer Policy."
  • If you use the Unity Integration approach to create instances of objects from the Exception Handling Application Block, you must use the non-static façade named ExceptionManager instead of the ExceptionPolicy class static façade.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.