Hi Dario, It's definitely the "inconsist...

2009-12-21T15:24:36.883+11:00

Hi Dario,

It's definitely the "inconsistency" (that's what I'm calling it and I'm sticking to it!!) between what ASP.NET displays and what's going execution-wise that's bothering me. You're right: the exception hierarchy is still intact.

Because we don't display friendly errors internally, my intention was to wrap a DirectoryNotFoundException with some additional context and specific instructions for correcting the problem. Setting up a new environment invariably throws up exceptions along the way when a specific configuration requirement isn't satisfied and this was to assist in those cases.

As far as I'm concerned as a naive developer, I've handled the inner exception and thrown the wrapper instead; it's the wrappaer message I feel ASP.NET should be presenting to me (in this particular case ;-). If I'm after the root cause I can dissect the stack trace.

Hi Michael I'm not sure I understand the prob...

2009-12-19T01:57:16.640+11:00

Hi Michael

I'm not sure I understand the problem. What you're seeing is how ASP.NET displays the exception. I don't understand how this affects handling in your own code.

ASP.NET is merely displaying the innermost exception (i.e. the root cause of the problem). With Reflector you can see this in the implementation of System.Web.UnhandledErrorFormatter (the class responsible for rendering the default error message). The PrepareFormatter() contains a loop where the innermost non-null InnerException is extracted and displayed.

This behaviour shouldn't affect your own error handling though. The exception hierarchy is still intact. Perhaps I've missed what you were getting at?

Comments on Dirty Words: Inner exception details displayed instead of wrapp...

Hi Dario, It's definitely the "inconsist...

Hi Michael I'm not sure I understand the prob...