CODEWITHSUNDEEP
asp.netexception
k80sg
k80sg

Reputation: 2473

asp.net + exceptions and redirecting

My intention is to log an error(I am using Log4Net) when an exception is caught and redirect to a pretty looking page with some error message. I have a class that returns a Type T object , mostly a DataSet.

In my Catch statement I wrote this, it works but I am not sure if there's a more appropriate way of handling, can someone please advice. Thanks. Note that the throw cannot be omitted because the class has a return type.:

      catch (Exception ex)
        {
            log.Error(ex);
            HttpContext.Current.Response.Redirect("~/errorPage.aspx");
            throw ex;
        }

Upvotes: 0

Views: 2185

Answers (1)

Paritosh
Paritosh

Reputation: 2379

It depends upon how you want to handle error on the page, In general , unhandled exception should be bubbled up to application_error in gloabl.asax file to it generic.Here is one simple way to handle this error.

void Application_Error(object sender, EventArgs e)
{
// Code that runs when an unhandled error occurs
// Get the exception object.
Exception exc = Server.GetLastError();

// Handle HTTP errors
if (exc.GetType() == typeof(HttpException))
{
// The Complete Error Handling Example generates
// some errors using URLs with "NoCatch" in them;
// ignore these here to simulate what would happen
// if a global.asax handler were not implemented.
  if (exc.Message.Contains("NoCatch") || exc.Message.Contains("maxUrlLength"))
  return;

//Redirect HTTP errors to HttpError page
  Server.Transfer("HttpErrorPage.aspx");
}

  // For other kinds of errors give the user some information
 // but stay on the default page
  Response.Write("<h2>Global Page Error</h2>\n");
 Response.Write(
  "<p>" + exc.Message + "</p>\n");
  Response.Write("Return to the <a href='Default.aspx'>" +
  "Default Page</a>\n");

 // Log the exception and notify system operators
 ExceptionUtility.LogException(exc, "DefaultPage");
 ExceptionUtility.NotifySystemOps(exc);

 // Clear the error from the server
 Server.ClearError();
}

Upvotes: 2

Related Questions