Centrelized Exceptions Catching?

[Picho]

Hi everyone.

I have an application that consumes several class libraries all written in
C#.

some of these DLL's are still buggy and produce exceptions. the application
is in its beta stage and therefor users are currently using it.

is there a way to avoid the built-in runtime exception handler and create a
mechanisem to collect the exception info and then lets say put it on a
Database? (exception can occur on the application, or any nested DLL in the
references path)

furthermore, when users get these messages, I instruct them to send me the
content of the message which is often usless since it does not contain line
numbers inside the code like it does in debug time, and it is almost
impossible for me to "recreate" the bug because the users dont allways
remember what they did prior to the exception...
so:
1. can I make the CLR show the line numbers (relaesing debug info in a way)?
2. can I recreate object states to recreate the situation leading to the
exception using info attached to the exception?

Thanx,

Picho

[Mohamoss]

Hi Picho
One I idea I just got it to a append the line number of the start of the
try to the catch to the exception message. Since you already had those in
Visual studio you can hardcode them to appear into your message
For example

102: try {


107 : }Catch ( Exception e){
MessageBox.Show("error in lines 102 to 107 : " + e.Message) ;
}
hope this helps
Mohamed Mahfouz
MEA Developer Support Center
ITworx on behalf of Microsoft EMEA GTSC

[Kieran Benton]

You might want to look at the Application.ThreadException event. That
will catch almost all exceptions that are not handled (excluding some
internal ones).

HTH
Kieran

mo************@egdsc.microsoft.com (Mohamoss) wrote in message news:<Br**************@cpmsftngxa06.phx.gbl>...

Hi Picho
One I idea I just got it to a append the line number of the start of the
try to the catch to the exception message. Since you already had those in
Visual studio you can hardcode them to appear into your message
For example

102: try {


107 : }Catch ( Exception e){
MessageBox.Show("error in lines 102 to 107 : " + e.Message) ;
}
hope this helps
Mohamed Mahfouz
MEA Developer Support Center
ITworx on behalf of Microsoft EMEA GTSC

[John Vottero]

"Picho" <pi***********@telhai.ac.il> wrote in message
news:eE****************@TK2MSFTNGP10.phx.gbl...

Hi everyone.

I have an application that consumes several class libraries all written in
C#.

some of these DLL's are still buggy and produce exceptions. the application is in its beta stage and therefor users are currently using it.

is there a way to avoid the built-in runtime exception handler and create a mechanisem to collect the exception info and then lets say put it on a
Database? (exception can occur on the application, or any nested DLL in the references path)

furthermore, when users get these messages, I instruct them to send me the
content of the message which is often usless since it does not contain line numbers inside the code like it does in debug time, and it is almost
impossible for me to "recreate" the bug because the users dont allways
remember what they did prior to the exception...
so:
1. can I make the CLR show the line numbers (relaesing debug info in a way)? 2. can I recreate object states to recreate the situation leading to the
exception using info attached to the exception?

You can open the Properties of the project and change the Release build to
include debug information. This will get you the line numbers. You should
also look into System.Application.ThreadException and
System.AppDomain.UnhandledException which let you set last chance condition
handlers.