views:

178

answers:

3

I want to be able to do logging in every catch block. Something like this.

catch (Exception exception)
{
  Logger.Write(exception);
}

and then the settings in the configuration will pick up the Message and StackTrace property etc using customer listener.

I would like to use Enterprise Library Logging Application Block. I'm sure someone must have done this already.

A: 

You need to add an appropriate listener for Text files - see this post, its for ASP.NET but the config files work the same way across applications.

RandomNoob
Can I do something to directly pass exception object so that it gives detailed stack trace etc. which will be helpful in debugging.
Ismail
+1  A: 

Microsoft has provided extensive guidance on this here: Developing Applications Using the Logging Application Block

It's well worth familiarizing yourself with what they have to say, as it's quite powerful.

If you want something a little more down to earth, some working examples are provided in this blog article: How To Configure and Use the Logging Application Block

If you're still having trouble after reading those, edit your post with more specific details about what seems to be the problem.

Andrew Anderson
Can I do something to directly pass exception object so that it gives detailed stack trace etc. which will be helpful in debugging?
Ismail
You could create a pretty simple method and/or string.format template and then use it when calling Logger.Write.
Andrew Anderson
+1  A: 

Others have posted some good links on getting the Logging Application Block (LAB) working so I won't duplicate that here.

In terms of formatting your exception you have 3 choices that I can think of:

  1. Use the default Exception.ToString() implementation (it's not bad)
  2. Write a Custom Formatter that integrates into the LAB.
  3. Write a helper function that performs the formatting and passes the string into the Write method.

If option 1 doesn't meet your needs then I would recommend going with option 3 (since option 2 is overkill).

A simple example would be something like:

    catch (Exception exception)
    {
        Logger.Write(LogHelper.CreateExceptionString(exception));
    }

    ...

    public static string CreateExceptionString(Exception e)
    {
        StringBuilder sb = new StringBuilder();
        CreateExceptionString(sb, e, string.Empty);

        return sb.ToString();
    }

    private static void CreateExceptionString(StringBuilder sb, Exception e, string indent)
    {
        if (indent == null)
        {
            indent = string.Empty;
        }
        else if (indent.Length > 0)
        {
            sb.AppendFormat("{0}Inner ", indent);
        }

        sb.AppendFormat("Exception Found:\n{0}Type: {1}", indent, e.GetType().FullName);
        sb.AppendFormat("\n{0}Message: {1}", indent, e.Message);
        sb.AppendFormat("\n{0}Source: {1}", indent, e.Source);
        sb.AppendFormat("\n{0}Stacktrace: {1}", indent, e.StackTrace);

        if (e.InnerException != null)
        {
            sb.Append("\n");
            CreateExceptionString(sb, e.InnerException, indent + "  ");
        }
    }
Tuzo
It is also helpful to include the name of the type of Exception. But otherwise quite nice.
Andrew Anderson
@Andrew: yeah or you could add some code to extract the IDictionary from the Data property.
Tuzo
Thank you very much Tuzo.
Ismail
I've got so many good responses to this question. I don't know why I'm not getting it on this other question. http://stackoverflow.com/questions/2942538/database-and-logic-layer-for-asp-net-mvc-application. And if the one answered is good then why people have not up voted it so that I can be sure of the answer.
Ismail