"Alvin Bruney [MVP]" <www.lulu.com/owcwrote in message
news:um****************@TK2MSFTNGP05.phx.gbl...
How would *inline page errors improve your situation? I marked inline page
errors because it doesn't really make sense to describe a page error as
inline. These are events that fire when an unhandled exception occurs at
the page level.
--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------
I was thinking in terms of how, for instance, PHP allows you to do the
following at the top of your code file:
register_exception_handler( 'functionName' );
Once you have done this, while this page executes any unhandled exceptions
will then be sent to that method before being passed up the stack. At that
point the programmer could, for instance, based on the exception return an
appropriate error response through the defined XML structure. This is what I
was hoping to do in .Net. I can't do this in Page_Error as defined in
Global.asax because this would, obviously, create a situation where an
invalid response was being sent for all but the one page the method was
coded to handle.
Carlo
