Download source - 7.03 KB

Introduction

Being ASP.NET developers, we develop a web project and get it completed in a month's time as there are many organizations which work on very tight bound timeline for developing web sites or web application projects, and deliver the project to the client within months. After project delivery, if the client come up saying that they are facing problems or application is giving errors, at that time it always becomes a headache for a developer to test each thing, even the whole project sometimes to find small errors (by means of error here, we are not talking about logical errors, we talking about exceptions which are mostly responsible for errors in the application). There are many exceptions which .NET framework fires which we never come to find out while debugging or developing the application. Those exceptions never directly affect the application but each small exception puts unnecessary load on the server. Here is the solution to track each and every small thing happening inside your ASP.NET web application, which I named as “Custom error tracking library”.

Implementing Custom Error Handling Library

The very first question that will come up is what is the core concept for this. Concept is that we will be maintaining an XML file with a predefined structure which I have built which will contain all the required fields as nodes and subs, which we call as errorlog.xml. There will be a CS library file which will track each and every minor error/exception that happens inside the application or .NET Framework and will put the error details inside the XML file. Once we get the CS library ready with us, we will just have a simple function with 2 overload methods as per the requirement in each try/catch blocks of the code and also in Application_Error event of Global.asax file.

XML File Structure for Error Logging

<xml version=”1.0? encoding=”utf-8?>
<errorlog>
  <error>
    <datetime>datetime</datetime>
    <filename>filename</filename>
    <classname>classname</classname>
    <methodname>methodname</methodname>
    <errormethod>errormethod</errormethod>
    <message>ErrorMessage</message>
    <errordetails>Details goes here</errordetails>
    <IP>IP address</IP>
    <url>URL</url>
  </error>
</errorlog>

Inside the root node of the XLM file <errorlog>, there will be a sub node <error> which will get duplicated for each error. For each error, the library will generate a node with all the below listed details in the XML file. Next to the last error node. So for each error, there will be a separate ERROR node. Each field of the above XML file is described below:

Datetime: Date and time of the error/exception
File name: File name where exception or error happens
Class name: Classname in which error occurred
Method name: Function name where there is an error
Error method: Name of the function which contains error code
Message: Error message/exception message
Error details: Detailed error description which will show the whole stack trace of the functional execution
IP: Client IP address
URL: Absolute error URL

Code Inside CS file (errorHandler.cs)

There will be a CS library file where we will write all the functionality for error handling and writing errors into XML file. errorHamdler.cs file will have two static methods named WriteError(). There will be two overloaded methods for the same functions with different parameters. CS file will look as given below. We name it as errorHamdler.cs.

using System;
using System.Collections.Generic;
using System.Text;
using System.Xml;
using System.Reflection;
using System.Diagnostics;
namespace TheCodeCenter
{
    public class errorHandler
    {
        string _strErrorMessage, _strDetails, _strClassName, _strMethodName;
        DateTime _dtOccuranceTime = new DateTime();
        public errorHandler()
        {

        }
        public errorHandler(DateTime time, string className, 
		string methodName, string errorMessage, string details)
        {
            _dtOccuranceTime = time;
            _strClassName = className;
            _strDetails = details;
            _strErrorMessage = errorMessage;
            _strMethodName = methodName;
        }
        public static void WriteError(Exception ex)
        {
            WriteError(ex, "");
        }
        public static void WriteError(Exception ex, string fileName)
        {
            XmlDocument doc = new XmlDocument();
            string strRootPath = System.Configuration.ConfigurationManager.AppSettings
				["logfilepath"].ToString();
            string xmlPath = System.Web.HttpContext.Current.Server.MapPath(strRootPath);
            doc.Load(@xmlPath);
            XmlNode newXMLNode, oldXMLNode;
            oldXMLNode = doc.ChildNodes[1].ChildNodes[0];
            newXMLNode = oldXMLNode.CloneNode(true);

            StackTrace stackTrace = new StackTrace();
            StackFrame stackFrame = stackTrace.GetFrame(1);
            MethodBase methodBase = stackFrame.GetMethod();

            newXMLNode.ChildNodes[0].InnerText = DateTime.Now.ToString();
            newXMLNode.ChildNodes[1].InnerText = fileName;
            newXMLNode.ChildNodes[2].InnerText = methodBase.DeclaringType.FullName;
            newXMLNode.ChildNodes[3].InnerText = methodBase.Name;
            newXMLNode.ChildNodes[4].InnerText = ex.TargetSite.Name;
            newXMLNode.ChildNodes[5].InnerText = ex.Message;
            newXMLNode.ChildNodes[6].InnerText = ex.StackTrace;
            newXMLNode.ChildNodes[7].InnerText = 
		System.Web.HttpContext.Current.Request.UserHostAddress;
            newXMLNode.ChildNodes[8].InnerText = 
		System.Web.HttpContext.Current.Request.Url.OriginalString;
            doc.ChildNodes[1].AppendChild(newXMLNode);
            doc.Save(@xmlPath);
            doc.RemoveAll();
        }
    }
}

Web.Config Settings

<appSettings>
	<add key="logfilepath" value="~/errorHandling/errorlog.xml"/>
</appSettings>

How to Use Error Handler in Application

Now everything is ready to be used in a real time application. In each try/catch block, we have to call Writeerror() function as described below:

protected void Page_Load(object sender, EventArgs e)
{
    throw new Exception("asds");

    try
    {
        int a = 0;
        int b = 10 / a;
        //throw new Exception("Custom error");
    }
    catch (Exception ex)
    {
        Response.Write(ex.Message);
        TheCodeCenter.errorHandler.WriteError(ex, "Default.aspx.vb");
    }
}

Apart from each try/catch block, we will put some code in the Global.asax file too, as given below:

void Application_Error(object sender, EventArgs e)
{
    object a = System.Web.HttpContext.Current.Request.ServerVariables["HTTP_REFERER"];
    TheCodeCenter.errorHandler.WriteError
	(Server.GetLastError().GetBaseException(), "Global.asax");
}

The reason behind putting code in Global.asax file is very important and necessary as there might be many exceptions which occurs at the application level and cannot be traceable in any try/catch blocks in any function or events. So any error except try/catch blocks will come in this event (Application_Error) and will get inserted into XML file. That’s it, we are done with the error handling, and all errors will be traceable from the XML file which is being generated via the error handler.

Implementing Custom Error Handling Library for ASP.NET using XML & C#.NET