Exception hierarchy in .NET in C Sharp (C#) - Time & Space Complexity

Time Complexity: Exception hierarchy in .NET

O(n)

Understanding Time Complexity

When working with exceptions in .NET, it's important to understand how the program handles errors internally.

We want to see how the time to handle exceptions grows as the number of exception types or hierarchy depth increases.

Scenario Under Consideration

Analyze the time complexity of catching exceptions in a hierarchy.

try
{
    // Some code that may throw exceptions
}
catch (ArgumentNullException ex)
{
    // Handle specific exception
}
catch (ArgumentException ex)
{
    // Handle more general exception
}
catch (Exception ex)
{
    // Handle all other exceptions
}
    

This code tries to catch exceptions starting from the most specific to the most general type.

Identify Repeating Operations

Identify the steps the runtime takes to find the right catch block.

• Primary operation: Checking exception type against each catch block in order.
• How many times: Up to the number of catch blocks until a match is found.

How Execution Grows With Input

As the number of catch blocks increases, the runtime checks more types to find a match.

Number of catch blocks (n)	Approx. Checks
3	Up to 3 checks
10	Up to 10 checks
100	Up to 100 checks

Pattern observation: The number of checks grows linearly with the number of catch blocks.

Final Time Complexity

Time Complexity: O(n)

This means the time to find the right exception handler grows in a straight line as more catch blocks are added.

Common Mistake

[X] Wrong: "Catching exceptions is always instant, no matter how many catch blocks there are."

[OK] Correct: The runtime checks each catch block in order, so more blocks mean more checks and longer handling time.

Interview Connect

Understanding how exception handling scales helps you write efficient error handling and shows you know how the runtime works behind the scenes.

Self-Check

"What if we reordered the catch blocks from general to specific? How would the time complexity change?"

Practice

1. Which class is the base class for all exceptions in .NET?

easy

A. System.Error

B. System.Exception

C. System.ApplicationException

D. System.SystemException

Solution

1. Step 1: Understand the exception hierarchy

   All exceptions in .NET inherit from a common base class to unify error handling.

2. Step 2: Identify the root base class

   The root base class for all exceptions is System.Exception, from which other exceptions derive.

3. Final Answer:

   System.Exception -> Option B

4. Quick Check:

   Base exception class = System.Exception [OK]

Hint: Remember: All exceptions come from System.Exception [OK]

Common Mistakes:

• Confusing System.SystemException as the base
• Thinking System.ApplicationException is the root
• Assuming System.Error exists in .NET

2. Which of the following is the correct syntax to catch a specific exception type ArgumentNullException in C#?

easy

A. catch (ArgumentNullException e) { }

B. catch ArgumentNullException (e) { }

C. catch (Exception e) { }

D. catch ArgumentNullException { }

Solution

1. Step 1: Recall catch block syntax

   In C#, to catch a specific exception, use catch (ExceptionType variable) syntax.

2. Step 2: Match the correct syntax for ArgumentNullException

   The correct syntax is catch (ArgumentNullException e) { }, which declares the exception type and variable.

3. Final Answer:

   catch (ArgumentNullException e) { } -> Option A

4. Quick Check:

   Correct catch syntax = catch (ExceptionType e) [OK]

Hint: Use parentheses around exception type and variable in catch [OK]

Common Mistakes:

• Omitting parentheses around exception type
• Using wrong order like catch ExceptionType (e)
• Not declaring a variable for the exception

3. What will be the output of the following C# code?

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

medium

A. General error caught

B. Compilation error

C. No output, program crashes

D. Index error caught

Solution

1. Step 1: Identify the exception thrown

   Accessing index 5 in an array of size 2 throws IndexOutOfRangeException.

2. Step 2: Check which catch block handles it

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

3. Final Answer:

   Index error caught -> Option D

4. Quick Check:

   Specific catch runs before general [OK]

Hint: Specific exceptions catch before general ones [OK]

Common Mistakes:

• Thinking general Exception catch runs first
• Assuming program crashes without catch
• Confusing IndexOutOfRangeException with ArgumentException

4. Identify the error in this code snippet:

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

medium

A. Catch-all block must be last

B. Catch blocks order is incorrect

C. No error, code is correct

D. Missing exception variable in catch blocks

Solution

1. Step 1: Review catch block syntax

   Catch blocks can omit the exception variable if not used, which is valid here.

2. Step 2: Check catch block order

   The specific FormatException catch is before the general catch-all block, which is correct.

3. Final Answer:

   No error, code is correct -> Option C

4. Quick Check:

   Catch-all last and variable optional [OK]

Hint: Catch-all must be last; variable optional in catch [OK]

Common Mistakes:

• Thinking catch-all must have variable
• Placing catch-all before specific catch
• Assuming variable is mandatory in catch

5. You want to catch all exceptions except NullReferenceException and handle them differently. Which approach correctly implements this in C#?

hard

A. Use a catch block for Exception and rethrow if NullReferenceException

B. Use a single catch block for Exception and check exception type inside

C. Use two catch blocks: one for NullReferenceException, one for Exception

D. Use a catch block for NullReferenceException only

Solution

1. Step 1: Understand the requirement

   We want to handle all exceptions except NullReferenceException differently, so we must detect and exclude it.

2. Step 2: Evaluate approaches

   Use a catch block for Exception and rethrow if NullReferenceException uses a general catch for Exception, then rethrows if the exception is NullReferenceException, effectively excluding it from handling.

3. Final Answer:

   Use a catch block for Exception and rethrow if NullReferenceException -> Option A

4. Quick Check:

   Rethrow to exclude specific exceptions [OK]

Hint: Rethrow specific exceptions inside general catch [OK]

Common Mistakes:

• Catching NullReferenceException first but not rethrowing
• Handling all exceptions in one catch without rethrow
• Using only NullReferenceException catch block