Finally block behavior in C Sharp (C#)

Introduction

The finally block lets you run code that must happen no matter what, like cleaning up or closing files.

You open a file and want to make sure it closes even if an error happens.

You start a network connection and need to close it whether the work succeeds or fails.

You allocate resources like memory or database connections and want to release them safely.

You want to show a message or log something after trying some code, regardless of errors.

Syntax

C Sharp (C#)

try
{
    // code that might cause an error
}
catch (Exception e)
{
    // code to handle the error
}
finally
{
    // code that always runs
}

The finally block runs after try and catch, no matter what.

You can use finally with or without a catch block.

Examples

This example shows a finally block without a catch. The message in finally always prints.

C Sharp (C#)

try
{
    Console.WriteLine("Trying something...");
}
finally
{
    Console.WriteLine("Always runs.");
}

This example catches an error and still runs the finally block.

C Sharp (C#)

try
{
    int x = 5 / 0;
}
catch (DivideByZeroException e)
{
    Console.WriteLine("Caught division by zero.");
}
finally
{
    Console.WriteLine("Cleanup code runs.");
}

Sample Program

This program tries to divide by zero, catches the error, and then runs the finally block. The program then continues normally.

C Sharp (C#)

using System;

class Program
{
    static void Main()
    {
        try
        {
            Console.WriteLine("Start try block.");
            int result = 10 / 0; // This causes an error
            Console.WriteLine("This line will not run.");
        }
        catch (DivideByZeroException)
        {
            Console.WriteLine("Caught division by zero error.");
        }
        finally
        {
            Console.WriteLine("Finally block always runs.");
        }
        Console.WriteLine("Program continues.");
    }
}

Important Notes

If there is a return inside try or catch, the finally block still runs before returning.

Use finally to release resources like files or connections safely.

Summary

The finally block runs no matter what happens in try or catch.

It is useful for cleanup tasks that must always happen.

You can use finally with or without catch.

Practice

1. What is the main purpose of the finally block in C# exception handling?

easy

A. To execute code regardless of whether an exception occurs or not

B. To catch exceptions thrown in the try block

C. To declare variables used in the try block

D. To stop the program when an exception occurs

Solution

1. Step 1: Understand the role of finally

   The finally block runs after the try and catch blocks, no matter what happens.

2. Step 2: Identify its purpose

   It is used to run cleanup code or important steps that must always execute, regardless of exceptions.

3. Final Answer:

   To execute code regardless of whether an exception occurs or not -> Option A

4. Quick Check:

   finally always runs [OK]

Hint: Remember: finally always runs, no matter what [OK]

Common Mistakes:

• Confusing finally with catch block
• Thinking finally only runs on exceptions
• Believing finally can catch exceptions

2. Which of the following is the correct syntax for using a finally block in C#?

easy

A. try { } catch { } finally { }

B. try { } finally { } catch { }

C. try { } catch { }

D. finally { } try { } catch { }

Solution

1. Step 1: Recall correct order of blocks

   In C#, the order is try, then catch (optional), then finally (optional).

2. Step 2: Match syntax

   Only try { } catch { } finally { } shows the correct order: try { } catch { } finally { }.

3. Final Answer:

   try { } catch { } finally { } -> Option A

4. Quick Check:

   Correct block order [OK]

Hint: Remember order: try, catch, then finally [OK]

Common Mistakes:

• Placing finally before catch
• Omitting try block
• Using finally without try

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

try {
    Console.WriteLine("Start");
    throw new Exception();
} catch {
    Console.WriteLine("Caught");
} finally {
    Console.WriteLine("Finally");
}

medium

A. Start\nFinally

B. Start\nCaught\nFinally

C. Caught\nFinally

D. Start\nCaught

Solution

1. Step 1: Trace the try block

   "Start" is printed, then an exception is thrown.

2. Step 2: Catch and finally execution

   The exception is caught, so "Caught" is printed, then the finally block runs printing "Finally".

3. Final Answer:

   Start\nCaught\nFinally -> Option B

4. Quick Check:

   try prints Start, catch prints Caught, finally prints Finally [OK]

Hint: Remember: finally runs after catch even if exception thrown [OK]

Common Mistakes:

• Ignoring catch block output
• Thinking finally runs before catch
• Missing the exception thrown in try

4. Identify the error in this C# code snippet:

try {
    Console.WriteLine("Hello");
} finally {
    Console.WriteLine("Cleanup");
} catch (Exception ex) {
    Console.WriteLine("Error");
}

medium

A. The catch block must come after finally

B. No error, code is correct

C. You cannot use finally without catch

D. The finally block must come after catch

Solution

1. Step 1: Check block order rules

   In C#, the finally block must come after all catch blocks.

2. Step 2: Identify incorrect order

   The code places finally before catch, which is invalid syntax.

3. Final Answer:

   The finally block must come after catch -> Option D

4. Quick Check:

   finally after catch [OK]

Hint: Remember: catch blocks come before finally [OK]

Common Mistakes:

• Placing finally before catch
• Thinking finally can be before catch
• Confusing order of blocks

5. Consider this code:

int result = 0;
try {
    result = 10 / 0;
} catch (DivideByZeroException) {
    result = 1;
} finally {
    result = 2;
}
Console.WriteLine(result);

What will be printed and why?

hard

A. 0, because division by zero stops execution before catch

B. 1, because catch sets result to 1 and finally does not change it

C. 2, because finally always runs and can overwrite result

D. Exception thrown, program crashes

Solution

1. Step 1: Analyze exception and catch block

   Division by zero throws DivideByZeroException, caught by catch which sets result = 1.

2. Step 2: Understand finally block effect

   The finally block runs after catch and sets result = 2, overwriting previous value.

3. Final Answer:

   2, because finally always runs and can overwrite result -> Option C

4. Quick Check:

   finally runs last and sets result = 2 [OK]

Hint: finally runs last and can overwrite variables set earlier [OK]

Common Mistakes:

• Assuming catch value stays after finally
• Thinking exception stops finally from running
• Believing program crashes without output