Why When clause in catch in C Sharp (C#)? - Purpose & Use Cases

The Big Idea

What if you could catch only the errors you want without messy checks inside your catch blocks?

The Scenario

Imagine you have a program that can throw many types of errors, and you want to handle some errors only if certain conditions are true. Without a way to check conditions in your error handler, you might end up writing many repeated catch blocks or complicated code inside catch blocks.

The Problem

Manually checking error details inside a catch block makes your code messy and hard to read. You might catch an error, then write extra if-statements to decide what to do. This slows down debugging and increases chances of mistakes.

The Solution

The When clause in catch lets you add a condition directly to the catch block. This means you only catch errors that meet your condition, keeping your code clean and clear. It helps you handle specific cases without extra checks inside the catch.

Before vs After

✗ Before

try {
  // code
} catch (Exception ex) {
  if (ex.Message.Contains("timeout")) {
    // handle timeout
  } else {
    throw;
  }
}

✓ After

try {
  // code
} catch (Exception ex) when (ex.Message.Contains("timeout")) {
  // handle timeout
}

What It Enables

This lets you write simpler, more readable error handling that reacts only to the exact problems you want to catch.

Real Life Example

For example, if your program calls a web service, you can catch only timeout errors to retry the request, while letting other errors pass through.

Key Takeaways

Manually checking errors inside catch blocks is messy and error-prone.

The When clause adds conditions directly to catch blocks for cleaner code.

This improves readability and precise error handling.

Practice

1.

What does the when clause do in a catch block in C#?

easy

A. It adds a condition to run the catch block only if the condition is true.

B. It defines a new exception type to catch.

C. It skips the catch block entirely.

D. It makes the catch block run before the try block.

Solution

1. Step 1: Understand the purpose of the when clause

   The when clause adds a condition to a catch block.

2. Step 2: Effect of the when clause in exception handling

   The catch block runs only if the condition after when is true, otherwise it skips.

3. Final Answer:

   It adds a condition to run the catch block only if the condition is true. -> Option A

4. Quick Check:

   when clause = conditional catch [OK]

Hint: when clause filters catch by condition [OK]

Common Mistakes:

• Thinking when defines a new exception type
• Assuming catch runs always regardless of when
• Confusing when with finally block

2.

Which of the following is the correct syntax to use a when clause in a catch block?

try {
    // code
} catch (Exception ex) _____ {
    // handle
}

easy

A. while (ex.Message.Contains("error"))

B. if (ex.Message.Contains("error"))

C. where (ex.Message.Contains("error"))

D. when (ex.Message.Contains("error"))

Solution

1. Step 1: Recall the correct keyword for condition in catch

   The correct keyword to add a condition in catch is when.

2. Step 2: Match the syntax with the options

   Only when (ex.Message.Contains("error")) uses when correctly with the condition.

3. Final Answer:

   when (ex.Message.Contains("error")) -> Option D

4. Quick Check:

   Use 'when' keyword for catch condition [OK]

Hint: Use 'when' keyword, not if/where/while in catch [OK]

Common Mistakes:

• Using if instead of when in catch
• Confusing when with where or while
• Missing parentheses after when

3.

What will be the output of this code?

try {
    throw new InvalidOperationException("Invalid operation");
} catch (InvalidOperationException ex) when (ex.Message.Contains("Invalid")) {
    Console.WriteLine("Caught invalid operation");
} catch (Exception) {
    Console.WriteLine("Caught general exception");
}

medium

A. Caught general exception

B. Caught invalid operation

C. No output

D. Runtime error

Solution

1. Step 1: Identify the thrown exception and matching catch

   The code throws InvalidOperationException with message containing "Invalid".

2. Step 2: Check the when condition in the first catch

   The first catch has a when clause checking if message contains "Invalid" which is true, so it runs.

3. Final Answer:

   Caught invalid operation -> Option B

4. Quick Check:

   when condition true runs first catch [OK]

Hint: Check exception type and when condition carefully [OK]

Common Mistakes:

• Ignoring the when condition and picking second catch
• Assuming no output if when is used
• Confusing exception types

4.

Find the error in this code snippet:

try {
    // some code
} catch (Exception ex) when ex.Message == "Error" {
    Console.WriteLine("Error caught");
}

medium

A. catch block must not have a condition

B. Cannot use when with Exception type

C. Missing parentheses around the when condition

D. Console.WriteLine is not allowed in catch

Solution

1. Step 1: Check syntax of when clause

   The condition after when must be enclosed in parentheses.

2. Step 2: Identify the missing parentheses in the code

   The code uses when ex.Message == "Error" without parentheses, which is invalid syntax.

3. Final Answer:

   Missing parentheses around the when condition -> Option C

4. Quick Check:

   when condition needs parentheses [OK]

Hint: Always put parentheses after when [OK]

Common Mistakes:

• Omitting parentheses around when condition
• Thinking when can't be used with Exception
• Believing catch can't have code inside

5.

Consider this code:

try {
    throw new ArgumentNullException("param");
} catch (ArgumentNullException ex) when (ex.ParamName == "param") {
    Console.WriteLine("Parameter error");
} catch (ArgumentNullException ex) {
    Console.WriteLine("Other argument null error");
}

What will be printed and why?

hard

A. Parameter error, because the when condition matches the ParamName.

B. Other argument null error, because when clause is ignored.

C. No output, because exception is not caught.

D. Runtime error due to duplicate catch blocks.

Solution

1. Step 1: Identify the thrown exception and its property

   The code throws ArgumentNullException with ParamName set to "param".

2. Step 2: Check the when clause condition in the first catch

   The first catch has a when clause checking if ex.ParamName == "param", which is true, so this catch runs.

3. Step 3: Understand catch block selection

   The second catch is ignored because the first matching catch with true when condition handles the exception.

4. Final Answer:

   Parameter error, because the when condition matches the ParamName. -> Option A

5. Quick Check:

   when true catches first matching block [OK]

Hint: when filters catch; first true condition wins [OK]

Common Mistakes:

• Ignoring when condition and picking second catch
• Thinking duplicate catch causes error
• Assuming exception is uncaught