Can we use multiple catch blocks in C#?

Question

0.00/5 (No votes)

See more:

Can use Multiple catch blocks?

What I have tried:

class student
{
try{
...
}
catch (Exception ex)
{
}
catch (Exception s)
{
}
finally()
{
}

}

Posted 14-Aug-18 0:13am

velmahesh

Updated 14-Aug-18 18:14pm

Add a Solution

2 solutions

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)

BillWoodruff · Accepted Answer · 2018-08-14T18:15:00

Yes, of course you can have multiple catch blocks in C#. As of C#6 you now have exception filters (VB.NET has had these a long time). See the section "Statement-level features" here: [^].

I strongly suggest you study these Exception handling guidelines from MS: [^].

F-ES Sitecore showed you a good example here, but there's one "feature" of that example I think is not good practice: having a "generic catch-all" that is going to "swallow" any Exception type you did not catch.

imho, good practice demands that you at least log an error that you "swallow." And, imho, best practice is to "never swallow," but re-throw if you must use a "catch-all."

F-ES Sitecore · Accepted Answer · 2018-08-14T00:19:00

Solution 1

If you want to use multiple catch blocks the exception type must be different

catch (ExceptionType1 a)
{
}
catch (ExceptionType2 b)
{
}
catch (ApplicationException c)
{
}
catch (Exception d)
{
}

When an exception is thrown it will check if the exception is type ExceptionType1, and if not it will go to the next catch and so on down the list until if finds a matching type.

Posted 14-Aug-18 0:19am

F-ES Sitecore

Comments

[no name] 14-Aug-18 7:32am

How can i define and add my own Exceptions?

F-ES Sitecore 14-Aug-18 8:03am

http://www.tutorialsteacher.com/csharp/custom-exception-csharp

Dave Kreskowiak 14-Aug-18 9:53am

You forgot to mention that catch order matters. From the documentation:
the order of the catch clauses is important because the catch clauses are examined in order. Catch the more specific exceptions before the less specific ones. The compiler produces an error if you order your catch blocks so that a later block can never be reached.

F-ES Sitecore 14-Aug-18 10:01am

> You forgot to mention that catch order matters.

You forgot to read my answer before you commented :)

BillWoodruff 15-Aug-18 0:28am

+4 Good answer; I've expressed my one reservation about the code in my post.

BillWoodruff 15-Aug-18 0:38am

fyi: re ApplicationExceptionre

Jeffery Richter in Framework Design Guidelines:

"System.ApplicationException is a class that should not be part of the .NET Framework. The original idea was that classes derived from SystemException would indicate exceptions thrown from the CLR (or system) itself, whereas non-CLR exceptions would be derived from ApplicationException. However, a lot of exception classes didn't follow this pattern. For example, TargetInvocationException (which is thrown by the CLR) is derived from ApplicationException. So, the ApplicationException class lost all meaning. The reason to derive from this base class is to allow some code higher up the call stack to catch the base class. It was no longer possible to catch all application exceptions."