Re: When to create your own exception class?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Yes, I use that approach too. I just wanted to point that instead of
spending a lot of time discussing is new exception types should be created
or not, we don´t have to miss the user's perspective and the user experience
when an exception happens.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

"Ignacio Machin ( .NET/ C# MVP )" <ignacio.machin AT dot.state.fl.us>
escribió en el mensaje news:uBRirdAfFHA.3880@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
>
> I prefer to use a mix approach, I present an user friendly message the
> most exact I can (sometimes there is nothing more to tell him but a "An
> error has occured, please reintent" or something similar )
> and a "Details" button that dump the StackTrace , Message of the catched
> exception as well as the inner exception.
> In this way when the user call or email me he can give a clue of what
> happened. I also create a .log file where I dump the error too.
>
> I agree with you that in general the user has no clue of what caused the
> error
>
> cheers,
>
> --
> Ignacio Machin,
> ignacio.machin AT dot.state.fl.us
> Florida Department Of Transportation
>

.

Quantcast