[RESOLVED] Error handling Question

Hello,
When my project goes live I think it would be preferable to redirect users to a custom error page rather than the dot.net page with the stack trace on, how do I implement this with try catch blocks?

In the forms pages I can use response.redirect but how do I handle this when the error occurs in one of my classes?

This is implementable through the Web.Config file.

Try googling Web.Config run time error redirecting. Multiple methods exist to get this done and you should find some examples quickly that way.

<customErrors defaultRedirect="defaulterrorpage.html"/>

But if I put a try catch in will it still show as an error and redirect i.e the only reason I am really want ing to put to finally block in to ensure open data connection are closed if an error occurs?

If you catch an error, it does not bubble up to the error handler (you handled it) unless you re-throw it.

If you rethrow it, then all code before rethrowing it occurs, all code after does not.

Thats what I mean, I still need to show an error page when an error occurs but I also need to ensure data connections get closed? How to do both?

Add a Finally to your Try/Catch block and close the connection there.

Thats what I have and that executes but then because the error has been handled (by the try catch finally) I cannot alert the user that an error occured i.e redirect to a custom errors page after.

You can ensure that your connections are closed within the Catch portion. After you've handled the error, do your checks, then rethrown some error (maybe a custom one) so that it redirects.

I have this in the classes sup proc

VB Code:

Catch ex As System.Exception
            If SqlCnnShippersCarriage.State = ConnectionState.Open Then
                SqlCnnShippersCarriage.Close()
            End If
            Throw New ApplicationException("An Error occured in DespatchNewCarriage")
        End Try

Then this in the web.config

VB Code:

<customErrors defaultRedirect="DefaultErrorPage.aspx"/>

This should work right?

Tried testing it with this but its not working it's just showing the standard "Unhandled overflow exception error page when it hits the second throw rether than redirecting to my Customised page?

VB Code:

AddToSessionInserts()
            Throw New OverflowException
        Catch ex As System.Exception
            If SqlCnnShippersCarriage.State = ConnectionState.Open Then
                SqlCnnShippersCarriage.Close()
            End If
            Throw New OverflowException
        End Try

Is it?

Yep even without the try catch stuff when I throw a completley unhandled exception it isnt using the custom errors redirect.

Fixed thanks all,
Dumb ass me forgot to set Mode="On"

Code:

---

  <customErrors mode="On" defaultRedirect="DefaultErrorPage.aspx"/>

---