Easiest possible error handling?

[Johnny Jörgensen]

Hi

Does anyone know of a component that can facilitate error handling in a
complex application.

What I'm looking for is a component you can simply drop on your application
form (or the like). If an exception occurs, it will generate a useful error
message containing procedure, line number etc for the offensive code and
either send it itself to a specified email address or give the user the
option of reporting the error.

Is that too much to ask? ;-)

Cheers,
Johnny J.

 

[rowe_newsgroups]

Hi

Does anyone know of a component that can facilitate error handling in a
complex application.

What I'm looking for is a component you can simply drop on your application
form (or the like). If an exception occurs, it will generate a useful error
message containing procedure, line number etc for the offensive code and
either send it itself to a specified email address or give the user the
option of reporting the error.

Is that too much to ask? ;-)

Cheers,
Johnny J.

Be a programmer and write your own! If you need help do a search in
this newsgroup for global exception handlers (Jay Harlow writes about
them all the time) and then just code in the email (hint, use
System.Net.Mail) and the other reporting bits. You should be exactly
what you want in very little time and then you wouldn't have to worry
about 3rd party code.

Thanks,

Seth Rowe

 

[Johnny Jörgensen]

I could do that, but that's not what I want. I want to be able to spend my
valuable time coding the things that matter instead...

But I don't want to get into a discussion about that, I simply want to know
if anybody knows a good control for that.

Cheers,
Johnny J.

Hi

Does anyone know of a component that can facilitate error handling in a
complex application.

What I'm looking for is a component you can simply drop on your
application
form (or the like). If an exception occurs, it will generate a useful
error
message containing procedure, line number etc for the offensive code and
either send it itself to a specified email address or give the user the
option of reporting the error.

Is that too much to ask? ;-)

Cheers,
Johnny J.

Be a programmer and write your own! If you need help do a search in
this newsgroup for global exception handlers (Jay Harlow writes about
them all the time) and then just code in the email (hint, use
System.Net.Mail) and the other reporting bits. You should be exactly
what you want in very little time and then you wouldn't have to worry
about 3rd party code.

Thanks,

Seth Rowe

 

[rowe_newsgroups]

I could do that, but that's not what I want. I want to be able to spend my

valuable time coding the things that matter instead...

Trust me, exception handling is one of the most valuable things you
can program. A terrific program that crashes expectantly is one area
will cause distrust of you and your applications. This is why I feel
you should take the time and write you own, as when it comes to
importance you shouldn't leave it up to others.

Besides, the simple email and MessageBox.Show(...) handling you
mentioned would probably take around an hour to write. Just subscripe
to the Application.ThreadException and AppDomain.UnhandledException
and use System.Net.Mail to send an email and program in the test you
want to use to determine if you should notify the user.

Thanks,

Seth Rowe

 

[Galen Somerville]

I could do that, but that's not what I want. I want to be able to spend my
valuable time coding the things that matter instead...

But I don't want to get into a discussion about that, I simply want to
know if anybody knows a good control for that.

Cheers,
Johnny J.




Be a programmer and write your own! If you need help do a search in
this newsgroup for global exception handlers (Jay Harlow writes about
them all the time) and then just code in the email (hint, use
System.Net.Mail) and the other reporting bits. You should be exactly
what you want in very little time and then you wouldn't have to worry
about 3rd party code.

Thanks,

Seth Rowe

mztools