You could also use the Exception Management Application Block, catch
unhandled exceptions, and publish them using a custom publisher. This would
have the advantage of giving you the ability to publish to the application
log simultaneously, while your custom publisher might screen exceptions and
only email certain ones (or just send an alert so the administrator could go
back and check the log).
"Andrew Banks" <ba****@nojunkblueyonder.co.uk> wrote in message
news:Ln*********************@news-text.cableinet.net...
Cheers Jim.
Email's not a problem!
"Jim Hughes" <NO*********@Hotmail.com> wrote in message
news:eq**************@TK2MSFTNGP11.phx.gbl... http://www.codeproject.com/dotnet/un...exceptions.asp will give you
a start, the email part is left up to you :)
"Andrew Banks" <ba****@nojunkblueyonder.co.uk> wrote in message
news:HS*********************@news-text.cableinet.net... Is it possible to trap all errors within a web app and do the
following
Send the user to another page "Error.aspx"
Send an email to myself with the filename and as much information
about the error as possible.
I take it this would be done in the Global.asax file but not too sure
where to start.
Any ideas greatly appreciated!
