How to get the exception from "try catch"

Question

1.00/5 (1 vote)

See more:

First of all,My project contains too many “try catch”，I worried that there is no complete exception message prompt，So I troubleshoot the error code position is very difficult。
I want to get an event that captures global exception information, and can get the complete exception information from "try catch"

In My project, there are too many lazy code

As follows：

C#

try
{
   //....throw a errr
}
catch{}

C#

try
{
  //....throw two  errr
}
catch(excetion ex)
{
   messagebox.show(ex.message);//but i want to know Stack
}

Such code too much

I need to see detailed information on the stack

Posted 4-Jun-15 5:26am

fengyuchun88

Updated 4-Jun-15 5:35am

F-ES Sitecore

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 4-Jun-15 17:34pm

From this question, I'm not sure that you understand exception propagation. If you have too many try-catch, its wrong. Each stack needs just one of just very few. Catching exception locally is a very bad thing. The best handling in no handling, letting the exceptions go.
—SA

4 solutions

Solution 2

You can display the stack trace to the user in a MessageBox object.

C#

try
{
  // Code or throw statement
}
catch(Exception ex)
{
  MessageBox.Show(ex.StackTrace);
}

Posted 4-Jun-15 6:01am

Mohamed El khames Bakir

Updated 4-Jun-15 9:25am

v2

Solution 4

My issue has been resolved, Thank you all! close

Posted 4-Jun-15 22:13pm

fengyuchun88

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Philippe Mori · Accepted Answer · 2015-06-04T15:36:00

To debug your application, you should run it under a debugger configured to stop on all exception as a starting point.

As indicated in a comment, you should avoid local try-catch when not necessary. You rarely need try/catch blocks in C#.

Usually, you might want to handle unhandled exception handling at application scope. A lot of information can be found on the web and in official MSDN documentation. By the way, since you are a beginner, it might make sense to read some books on C# first.

http://www.csharp-examples.net/catching-unhandled-exceptions/[^]

Both of you sample code are usually wrong. You rarely want to swallow exception as in first example and if you write a message to the user, you will typically give him a proper message and not use the original message.

For some type of application were safety or intellectual property are important, you really don't want to display the stack trace as it can give some crucial information.

F-ES Sitecore · Accepted Answer · 2015-06-04T05:34:00

Solution 1

https://msdn.microsoft.com/en-us/library/system.exception.stacktrace(v=vs.110).aspx[^]

Posted 4-Jun-15 5:34am