Why Finally block behavior in C Sharp (C#)? - Purpose & Use Cases

The Big Idea

What if your program could always clean up after itself, no matter what errors happen?

The Scenario

Imagine you are writing a program that opens a file to read data. You have to make sure the file is always closed after reading, no matter what happens during the reading process.

If you try to do this manually by writing code to close the file after every possible step, it quickly becomes confusing and easy to forget.

The Problem

Manually closing resources like files or database connections is slow and error-prone. If an error happens, your program might skip the closing step, causing resource leaks or crashes later.

This makes your code messy and unreliable.

The Solution

The finally block in C# solves this problem by guaranteeing that certain code runs no matter what -- even if an error occurs or the program returns early.

This means you can put cleanup code like closing files inside finally, and be sure it always runs.

Before vs After

✗ Before

try {
  // read file
  // close file
} catch {
  // handle error
  // close file again?
}

✓ After

try {
  // read file
} catch {
  // handle error
} finally {
  // close file
}

What It Enables

It enables you to write safer, cleaner code that always cleans up resources, preventing bugs and crashes.

Real Life Example

When downloading a file from the internet, you want to make sure the connection is closed even if the download fails halfway. Using finally ensures the connection closes properly every time.

Key Takeaways

Manually managing cleanup is error-prone and messy.

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

This guarantees important cleanup code always executes.