How to test for HttpException

[Guest]

I have this code in Global.asax, but it doesn't compile yet.
What am i doing wrong?
protected void Application_Error(Object sender, EventArgs e)
{
Exception objErr = Server.GetLastError().GetBaseException();
string msg = objErr.ToString();
if (objErr.GetType is HttpException)
{
// Need to bypass 404 errors
ErrNotify.LogError(msg);
}
else
{
ErrNotify.LogError(msg);
}
Server.ClearError();
}

 

[Laurent Bugnion]

Hi,

I have this code in Global.asax, but it doesn't compile yet.
What am i doing wrong?
protected void Application_Error(Object sender, EventArgs e)
{
Exception objErr = Server.GetLastError().GetBaseException();
string msg = objErr.ToString();

I would rather use

string msg = objErr.Message;

if (objErr.GetType is HttpException)

That should be

if ( objErr is HttpException )

{
// Need to bypass 404 errors
ErrNotify.LogError(msg);
}
else
{
ErrNotify.LogError(msg);

Did you notice that you do exactly the same in both cases?

}
Server.ClearError();
}

HTH,
Laurent

 

[Dave Sexton]

Hi Laurent,

I would rather use

string msg = objErr.Message;

Exception.ToString() provides details such as the StackTrace and the
StackTraces of the InnerException (recursively). Also, when deriving from
Exception you can override ToString to add more details about the exception
that the Message property doesn't provide.

So for error logging purposes, such as the OP's code, ToString is probably a
better choice.

<snip>

 

[Laurent Bugnion]

Hi Dave,

Hi Laurent,



Exception.ToString() provides details such as the StackTrace and the
StackTraces of the InnerException (recursively). Also, when deriving from
Exception you can override ToString to add more details about the exception
that the Message property doesn't provide.

So for error logging purposes, such as the OP's code, ToString is probably a
better choice.

<snip>

Yes, you're right. Don't know why, I was sure that the OP used msg to
display a warning to the user.

Greetings,
Laurent