Best way to debug
-
I'm at a position where I cannot step thru my code to see where my problem is at. So I've got message boxes everywhere catching exception. So what is the best way to debug when you can't be there. Right now I'm catching the exception showing the message, the source, and the stack trace. Which I must admit is a little confusing. Any other suggestions. Thanks
Tom Wright tawright915@yahoo.com
-
I'm at a position where I cannot step thru my code to see where my problem is at. So I've got message boxes everywhere catching exception. So what is the best way to debug when you can't be there. Right now I'm catching the exception showing the message, the source, and the stack trace. Which I must admit is a little confusing. Any other suggestions. Thanks
Tom Wright tawright915@yahoo.com
Why do you say you cannot debug through your code? I think you could use catch (Exception ex) { System.Diagnostics.Trace.WriteLine(ex.Message + " " + ex.StackTrace); }
-
I'm at a position where I cannot step thru my code to see where my problem is at. So I've got message boxes everywhere catching exception. So what is the best way to debug when you can't be there. Right now I'm catching the exception showing the message, the source, and the stack trace. Which I must admit is a little confusing. Any other suggestions. Thanks
Tom Wright tawright915@yahoo.com
It is the most arduous but it really works when it has too.
A man said to the universe: "Sir I exist!" "However," replied the Universe, "The fact has not created in me A sense of obligation." -- Stephen Crane
-
Why do you say you cannot debug through your code? I think you could use catch (Exception ex) { System.Diagnostics.Trace.WriteLine(ex.Message + " " + ex.StackTrace); }
I'm sorry, I meant I cannot step thru my code to see where my problem is at. Reason is this is socket app that requires a secured connection and that is on a network on the east coast.....I'm in the midwest. Currently I am do the try and catch but putting it to a message box instead of the Trace function. I'll try that and see what the results are. Thanks
Tom Wright tawright915@yahoo.com
-
I'm sorry, I meant I cannot step thru my code to see where my problem is at. Reason is this is socket app that requires a secured connection and that is on a network on the east coast.....I'm in the midwest. Currently I am do the try and catch but putting it to a message box instead of the Trace function. I'll try that and see what the results are. Thanks
Tom Wright tawright915@yahoo.com
When you use Trace you can have the code running without pressing the OK of the MessageBox and writing down the message on a piece of paper, while all the messages are going to be written in the Output window, so I would say it's more convenient. I hope it helps. Cheers