Why Multiple catch blocks in C Sharp (C#)? - Purpose & Use Cases

The Big Idea

What if you could catch each problem exactly where it happens and fix it perfectly every time?

The Scenario

Imagine you write a program that reads a file and then divides numbers. If something goes wrong, like the file is missing or you try to divide by zero, you want to handle each problem differently.

Without multiple catch blocks, you have to guess what error happened or write complicated code to check the error type manually.

The Problem

Handling all errors in one place means you can't respond properly to each problem. You might show the wrong message or miss fixing the real issue.

This makes your code messy, hard to read, and easy to break when new errors appear.

The Solution

Multiple catch blocks let you write separate code for each type of error. This way, you can give clear messages and fix problems exactly where they happen.

Your code becomes cleaner, easier to understand, and safer to run.

Before vs After

✗ Before

try {
  // code that may throw different exceptions
} catch (Exception e) {
  if (e is FileNotFoundException) {
    // handle file error
  } else if (e is DivideByZeroException) {
    // handle divide error
  }
}

✓ After

try {
  // code that may throw different exceptions
} catch (FileNotFoundException e) {
  // handle file error
} catch (DivideByZeroException e) {
  // handle divide error
}

What It Enables

You can handle each error type clearly and safely, making your program more reliable and user-friendly.

Real Life Example

When building a calculator app that reads user input from a file, you can catch file errors separately from math errors, so users get helpful messages for each problem.

Key Takeaways

Multiple catch blocks separate error handling by type.

This makes code cleaner and easier to maintain.

It helps programs respond correctly to different problems.

Practice

1.

What is the main purpose of using multiple catch blocks in C#?

easy

A. To avoid using try blocks

B. To handle different types of exceptions separately

C. To make the code run faster

D. To declare multiple variables

Solution

1. Step 1: Understand the role of catch blocks

   catch blocks are used to handle errors that happen in the try block.

2. Step 2: Recognize why multiple catch blocks are used

   Using multiple catch blocks lets you respond differently to different error types, making your program clearer and safer.

3. Final Answer:

   To handle different types of exceptions separately -> Option B

4. Quick Check:

   Multiple catch blocks = handle different exceptions [OK]

Hint: Multiple catch blocks handle different errors separately [OK]

Common Mistakes:

• Thinking multiple catch blocks speed up code
• Believing catch blocks replace try blocks
• Using catch blocks to declare variables

2.

Which of the following is the correct syntax order for multiple catch blocks in C#?

try { ... }
catch (ArgumentNullException e) { ... }
catch (Exception e) { ... }

easy

A. Specific exceptions first, general exceptions last

B. General exceptions first, specific exceptions last

C. Order does not matter

D. Only one catch block is allowed

Solution

1. Step 1: Understand exception hierarchy

   Specific exceptions like ArgumentNullException inherit from general exceptions like Exception.

2. Step 2: Order catch blocks correctly

   Place specific exceptions first so they catch their errors before the general catch block handles all others.

3. Final Answer:

   Specific exceptions first, general exceptions last -> Option A

4. Quick Check:

   Specific before general catch blocks [OK]

Hint: Put specific exceptions before general ones in catch blocks [OK]

Common Mistakes:

• Placing general catch before specific causes unreachable code
• Assuming catch order does not matter
• Trying to use multiple catch blocks without try

3.

What will be the output of this C# code?

try {
    int[] arr = new int[2];
    Console.WriteLine(arr[5]);
} catch (IndexOutOfRangeException) {
    Console.WriteLine("Index error caught");
} catch (Exception) {
    Console.WriteLine("General error caught");
}

medium

A. No output, program crashes

B. General error caught

C. Index error caught

D. Compilation error

Solution

1. Step 1: Identify the exception thrown

   Accessing arr[5] causes an IndexOutOfRangeException because the array size is 2.

2. Step 2: Match exception to catch block

   The first catch block matches IndexOutOfRangeException, so it runs and prints "Index error caught".

3. Final Answer:

   Index error caught -> Option C

4. Quick Check:

   IndexOutOfRangeException triggers first catch [OK]

Hint: Exception type matches first suitable catch block [OK]

Common Mistakes:

• Thinking general catch runs before specific
• Assuming no exception occurs
• Confusing exception types

4.

Find the error in this code snippet:

try {
    int x = int.Parse("abc");
} catch (Exception e) {
    Console.WriteLine("General error");
} catch (FormatException e) {
    Console.WriteLine("Format error");
}

medium

A. The FormatException catch block is unreachable

B. Missing finally block

C. Try block syntax is incorrect

D. No error, code is correct

Solution

1. Step 1: Check catch block order

   The first catch block catches all Exception types, including FormatException.

2. Step 2: Identify unreachable catch block

   Since Exception catch is first, the FormatException catch block can never run, causing a compile error.

3. Final Answer:

   The FormatException catch block is unreachable -> Option A

4. Quick Check:

   General catch before specific causes unreachable code [OK]

Hint: Place specific catch blocks before general ones to avoid unreachable code [OK]

Common Mistakes:

• Putting general catch before specific
• Ignoring unreachable code errors
• Thinking finally block is mandatory

5.

You want to handle NullReferenceException and DivideByZeroException differently, but also catch any other exceptions generally. Which is the best order of catch blocks?

try {
    // code that may throw exceptions
} catch (___) {
    Console.WriteLine("Null reference error");
} catch (___) {
    Console.WriteLine("Divide by zero error");
} catch (___) {
    Console.WriteLine("Other error");
}

hard

A. Exception, DivideByZeroException, NullReferenceException

B. Exception, NullReferenceException, DivideByZeroException

C. DivideByZeroException, Exception, NullReferenceException

D. NullReferenceException, DivideByZeroException, Exception

Solution

1. Step 1: Identify specific exceptions

   NullReferenceException and DivideByZeroException are specific exceptions to catch first.

2. Step 2: Place general exception last

   The general Exception catch block should come last to catch all other exceptions.

3. Final Answer:

   NullReferenceException, DivideByZeroException, Exception -> Option D

4. Quick Check:

   Specific exceptions first, general last [OK]

Hint: Catch specific exceptions before general Exception last [OK]

Common Mistakes:

• Putting Exception catch first
• Mixing order of specific exceptions
• Omitting general catch block