how do you stop the asp worker processing errors

[Henry]

Where are the templates for the asp.net error pages stored? I am
catching all errors but sometimes I still get the orange asp error
page.
I looked at machine.config but I didn't see any error handler which I
could overwrite. I don't want my customers to see the aspxerror path
in the URL either.
Does someone know how to replace the error handling in asp.net at the
root? I don't mean the customerrors tag in web.config. That's too late
in the process for me.
Thanks, Henry

[Jim Cheshire [MSFT]]

Hi Henry,

I'm not exactly sure what you're asking, but if you're trying to handle any
unhandled exception, the best method is to add an event delegate for
AppDomain.CurrentDomain.UnhandledException.

Jim Cheshire [MSFT]
MCP+I, MCSE, MCSD, MCDBA
Microsoft Developer Support
ja******@online.microsoft.com

This post is provided "AS-IS" with no warranties and confers no rights.

--------------------

From: ne********@bestmail.us (Henry)
Newsgroups: microsoft.public.dotnet.framework.aspnet
Subject: how do you stop the asp worker processing errors
Date: 21 Jul 2004 10:02:38 -0700
Organization: http://groups.google.com
Lines: 10
Message-ID: <d8**************************@posting.google.com >
NNTP-Posting-Host: 67.100.95.19
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1090429372 14086 127.0.0.1 (21 Jul 2004 17:02:52 GMT)X-Complaints-To: gr**********@google.com
NNTP-Posting-Date: Wed, 21 Jul 2004 17:02:52 +0000 (UTC)
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!p
ostnews2.google.com!not-for-mailXref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:248881
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

Where are the templates for the asp.net error pages stored? I am
catching all errors but sometimes I still get the orange asp error
page.
I looked at machine.config but I didn't see any error handler which I
could overwrite. I don't want my customers to see the aspxerror path
in the URL either.
Does someone know how to replace the error handling in asp.net at the
root? I don't mean the customerrors tag in web.config. That's too late
in the process for me.
Thanks, Henry

[John Saunders]

"Henry" <ne********@bestmail.us> wrote in message
news:d8**************************@posting.google.c om...

Where are the templates for the asp.net error pages stored? I am
catching all errors but sometimes I still get the orange asp error
page.
I looked at machine.config but I didn't see any error handler which I
could overwrite. I don't want my customers to see the aspxerror path
in the URL either.
Does someone know how to replace the error handling in asp.net at the
root? I don't mean the customerrors tag in web.config. That's too late
in the process for me.

Take a look at the <customErrors> element.
--
John Saunders
johnwsaundersiii at hotmail

[Marcos Santos \(MOS\)]

Hi, you could redirect your user to another page (friendly-PageError)

in your web.config you could do:

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

so whenever an unhandled error is created automaticly redirects to
AppError.aspx

Marcos Santos

"Henry" <ne********@bestmail.us> escreveu na mensagem
news:d8**************************@posting.google.c om...

Where are the templates for the asp.net error pages stored? I am
catching all errors but sometimes I still get the orange asp error
page.
I looked at machine.config but I didn't see any error handler which I
could overwrite. I don't want my customers to see the aspxerror path
in the URL either.
Does someone know how to replace the error handling in asp.net at the
root? I don't mean the customerrors tag in web.config. That's too late
in the process for me.
Thanks, Henry

[Henry]

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

I played with the custom errors but it always will result to a URL
like this:

AppError.aspx&aspxerrorpath=/ErrorHandling/WebForm1.aspx

asp will always append the error path at the end of my custom error
handler and I don't want this.

There must be a way to catch errors (404,500, ...) before the custom
error handler gets them.

Henry

[Jim Cheshire [MSFT]]

Henry,

You can either use IIS error handling or write an HttpModule to do that.

Jim Cheshire [MSFT]
MCP+I, MCSE, MCSD, MCDBA
Microsoft Developer Support
ja******@online.microsoft.com

This post is provided "AS-IS" with no warranties and confers no rights.

--------------------

From: ne********@bestmail.us (Henry)
Newsgroups: microsoft.public.dotnet.framework.aspnet
Subject: Re: how do you stop the asp worker processing errors
Date: 22 Jul 2004 09:33:56 -0700
Organization: http://groups.google.com
Lines: 16
Message-ID: <d8**************************@posting.google.com >
References: <d8**************************@posting.google.com > <OZ**************@TK2MSFTNGP11.phx.gbl>NNTP-Posting-Host: 67.100.95.19
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1090514036 17900 127.0.0.1 (22 Jul 2004 16:33:56 GMT)X-Complaints-To: gr**********@google.com
NNTP-Posting-Date: Thu, 22 Jul 2004 16:33:56 +0000 (UTC)
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!fr.ip.ndsoftware.net!proxad.net!postnews 2.google.
com!not-for-mailXref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:249140
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

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

I played with the custom errors but it always will result to a URL
like this:

AppError.aspx&aspxerrorpath=/ErrorHandling/WebForm1.aspx

asp will always append the error path at the end of my custom error
handler and I don't want this.

There must be a way to catch errors (404,500, ...) before the custom
error handler gets them.

Henry