About Error handling in ASPX pages

[Lau Lei Cheong]

Hello,

I'm currently using Application_Err or method in Global.asax.cs to handle
errors.

Recently, I heard about Page.ErrorPage and plan to use it for handling
errors on certain pages. Are there any major difference in using these
methods? My concern is mainly on the restrictions imposed on using these
method.

In my old error handling routine, I tried to use Server.GetLatEr ror() to
get Exception object in the error page redirected by Response.Redire ct() but
failed, can I use this method to retrieve the exception object in the new
page if Page.ErrorPage is used instead?

Thanks a lot.

Regards,
Lau Lei Cheong
--
If you want to mail to me, please replace all instance of "e" to "a" in my
email address. Thank you.
Sorry for any inconvience caused, but there's many spam-mailers.

[Scott M.]

In ASP.NET you use structured exception handling via Try..End Try
statements. These statements allow you to catch exceptions, handle
different exceptions differently and keep your application going.

Try
some code that may throw an exception
Catch ex as Exception
some code to handle the exception
the exception itself is accessible via the variable name given to
it on the "Catch" line, so we can find out what type of exception we
have:

ex.getType.ToSt ring

we can get the exception message:

ex.message
End Try

"Lau Lei Cheong" <le****@yehoo.c om.hk> wrote in message
news:Om******** ******@TK2MSFTN GP09.phx.gbl...

Hello,

I'm currently using Application_Err or method in Global.asax.cs to
handle
errors.

Recently, I heard about Page.ErrorPage and plan to use it for handling
errors on certain pages. Are there any major difference in using these
methods? My concern is mainly on the restrictions imposed on using these
method.

In my old error handling routine, I tried to use Server.GetLatEr ror()
to
get Exception object in the error page redirected by Response.Redire ct()
but
failed, can I use this method to retrieve the exception object in the new
page if Page.ErrorPage is used instead?

Thanks a lot.

Regards,
Lau Lei Cheong
--
If you want to mail to me, please replace all instance of "e" to "a" in my
email address. Thank you.
Sorry for any inconvience caused, but there's many spam-mailers.

[George Durzi]

You should also look into the
Microsoft.Appli cationBlocks.Ex ceptionManageme nt application block. It
provides some great functionality. Plus, they've already built and tested
it, so you don't have to.

"Scott M." <s-***@nospam.nosp am> wrote in message
news:On******** ******@TK2MSFTN GP10.phx.gbl...

In ASP.NET you use structured exception handling via Try..End Try
statements. These statements allow you to catch exceptions, handle
different exceptions differently and keep your application going.

Try
some code that may throw an exception
Catch ex as Exception
some code to handle the exception
the exception itself is accessible via the variable name given to
it on the "Catch" line, so we can find out what type of exception we
have:

ex.getType.ToSt ring

we can get the exception message:

ex.message
End Try

"Lau Lei Cheong" <le****@yehoo.c om.hk> wrote in message
news:Om******** ******@TK2MSFTN GP09.phx.gbl...

Hello,

I'm currently using Application_Err or method in Global.asax.cs to
handle
errors.

Recently, I heard about Page.ErrorPage and plan to use it for handling errors on certain pages. Are there any major difference in using these
methods? My concern is mainly on the restrictions imposed on using these
method.

In my old error handling routine, I tried to use Server.GetLatEr ror()
to
get Exception object in the error page redirected by Response.Redire ct()
but
failed, can I use this method to retrieve the exception object in the new page if Page.ErrorPage is used instead?

Thanks a lot.

Regards,
Lau Lei Cheong
--
If you want to mail to me, please replace all instance of "e" to "a" in my email address. Thank you.
Sorry for any inconvience caused, but there's many spam-mailers.

[Lau Lei Cheong]

True. However since the page is used to handle exceptions not on specific
task(such as when ASP.NET detects dangerous value in Request.Form[]) and
also unexpected server error, I think a general form of error handling would
be more appropiate.

"Scott M." <s-***@nospam.nosp am> ¦b¶l¥ó
news:On******** ******@TK2MSFTN GP10.phx.gbl ¤¤¼¶¼g...

In ASP.NET you use structured exception handling via Try..End Try
statements. These statements allow you to catch exceptions, handle
different exceptions differently and keep your application going.

Try
some code that may throw an exception
Catch ex as Exception
some code to handle the exception
the exception itself is accessible via the variable name given to
it on the "Catch" line, so we can find out what type of exception we
have:

ex.getType.ToSt ring

we can get the exception message:

ex.message
End Try

"Lau Lei Cheong" <le****@yehoo.c om.hk> wrote in message
news:Om******** ******@TK2MSFTN GP09.phx.gbl...

Hello,

I'm currently using Application_Err or method in Global.asax.cs to
handle
errors.

Recently, I heard about Page.ErrorPage and plan to use it for handling errors on certain pages. Are there any major difference in using these
methods? My concern is mainly on the restrictions imposed on using these
method.

In my old error handling routine, I tried to use Server.GetLatEr ror()
to
get Exception object in the error page redirected by Response.Redire ct()
but
failed, can I use this method to retrieve the exception object in the new page if Page.ErrorPage is used instead?

Thanks a lot.

Regards,
Lau Lei Cheong
--
If you want to mail to me, please replace all instance of "e" to "a" in my email address. Thank you.
Sorry for any inconvience caused, but there's many spam-mailers.

[Lau Lei Cheong]

Thanks for your information. This seems to be something interesting. :)

I'm learning how to build the interface through it.

"George Durzi" <gd****@hotmail .com> ¦b¶l¥ó
news:uI******** ********@TK2MSF TNGP10.phx.gbl ¤¤¼¶¼g...

You should also look into the
Microsoft.Appli cationBlocks.Ex ceptionManageme nt application block. It
provides some great functionality. Plus, they've already built and tested
it, so you don't have to.

"Scott M." <s-***@nospam.nosp am> wrote in message
news:On******** ******@TK2MSFTN GP10.phx.gbl...

In ASP.NET you use structured exception handling via Try..End Try
statements. These statements allow you to catch exceptions, handle
different exceptions differently and keep your application going.

Try
some code that may throw an exception
Catch ex as Exception
some code to handle the exception
the exception itself is accessible via the variable name given to
it on the "Catch" line, so we can find out what type of exception we
have:

ex.getType.ToSt ring

we can get the exception message:

ex.message
End Try

"Lau Lei Cheong" <le****@yehoo.c om.hk> wrote in message
news:Om******** ******@TK2MSFTN GP09.phx.gbl...

Hello,

I'm currently using Application_Err or method in Global.asax.cs to
handle
errors.

Recently, I heard about Page.ErrorPage and plan to use it for handling errors on certain pages. Are there any major difference in using these
methods? My concern is mainly on the restrictions imposed on using these method.

In my old error handling routine, I tried to use Server.GetLatEr ror() to
get Exception object in the error page redirected by Response.Redire ct() but
failed, can I use this method to retrieve the exception object in the new page if Page.ErrorPage is used instead?

Thanks a lot.

Regards,
Lau Lei Cheong
--
If you want to mail to me, please replace all instance of "e" to "a"

in

my email address. Thank you.
Sorry for any inconvience caused, but there's many spam-mailers.

[Scott M.]

I understand, but Page.ErrorPage isn't an error handler. It is just a
designation as to which page to show when there is an unhandled error.
"Lau Lei Cheong" <le****@yehoo.c om.hk> wrote in message
news:ea******** ******@tk2msftn gp13.phx.gbl...

True. However since the page is used to handle exceptions not on specific
task(such as when ASP.NET detects dangerous value in Request.Form[]) and
also unexpected server error, I think a general form of error handling
would
be more appropiate.

"Scott M." <s-***@nospam.nosp am> ¦b¶l¥ó
news:On******** ******@TK2MSFTN GP10.phx.gbl ¤¤¼¶¼g...

In ASP.NET you use structured exception handling via Try..End Try
statements. These statements allow you to catch exceptions, handle
different exceptions differently and keep your application going.

Try
some code that may throw an exception
Catch ex as Exception
some code to handle the exception
the exception itself is accessible via the variable name given to
it on the "Catch" line, so we can find out what type of exception we
have:

ex.getType.ToSt ring

we can get the exception message:

ex.message
End Try

"Lau Lei Cheong" <le****@yehoo.c om.hk> wrote in message
news:Om******** ******@TK2MSFTN GP09.phx.gbl...

> Hello,
>
> I'm currently using Application_Err or method in Global.asax.cs to
> handle
> errors.
>
> Recently, I heard about Page.ErrorPage and plan to use it for handling > errors on certain pages. Are there any major difference in using these
> methods? My concern is mainly on the restrictions imposed on using
> these
> method.
>
> In my old error handling routine, I tried to use
> Server.GetLatEr ror()
> to
> get Exception object in the error page redirected by
> Response.Redire ct()
> but
> failed, can I use this method to retrieve the exception object in the new > page if Page.ErrorPage is used instead?
>
> Thanks a lot.
>
> Regards,
> Lau Lei Cheong
> --
> If you want to mail to me, please replace all instance of "e" to "a" in my > email address. Thank you.
> Sorry for any inconvience caused, but there's many spam-mailers.
>
>