Why use finally in C#?

by

The code inside a finally block will get executed regardless of whether or not there is an exception. This comes in very handy when it comes to certain housekeeping functions you need to always run like closing connections.

Now, I’m guessing your question is why you should do this:

try
{
    doSomething();
}
catch
{
    catchSomething();
}
finally
{
    alwaysDoThis();
}

When you can do this:

try
{
    doSomething();
}
catch
{
    catchSomething();
}

alwaysDoThis();

The answer is that a lot of times the code inside your catch statement will either rethrow an exception or break out of the current function. With the latter code, the “alwaysDoThis();” call won’t execute if the code inside the catch statement issues a return or throws a new exception.

More Related Contents:

  1. How to keep running a program if an exception occurs? [duplicate]
  2. Is there a difference between “throw” and “throw ex”?
  3. WPF global exception handler [duplicate]
  4. Best practices for catching and re-throwing .NET exceptions
  5. Catch an exception thrown by an async void method
  6. Globally catch exceptions in a WPF application?
  7. Get connection string from App.config
  8. UnauthorizedAccessException cannot resolve Directory.GetFiles failure [duplicate]
  9. catch exception that is thrown in different thread
  10. .NET Global exception handler in console application
  11. Is there a reason Image.FromFile throws an OutOfMemoryException for an invalid image format?
  12. How to use ELMAH to manually log errors
  13. What’s the difference between Application.ThreadException and AppDomain.CurrentDomain.UnhandledException?
  14. What happens if a finally block throws an exception?
  15. File access error with FileSystemWatcher when multiple files are added to a directory
  16. The calling thread cannot access this object because a different thread owns it [duplicate]
  17. How can I catch a 404?
  18. How can I make a background worker thread set to Single Thread Apartment?
  19. Why is try {…} finally {…} good; try {…} catch{} bad?
  20. When to use try/catch blocks?
  21. Wrong line number on stack trace
  22. How to catch ALL exceptions/crashes in a .NET app [duplicate]
  23. How to check if IOException is Not-Enough-Disk-Space-Exception type?
  24. Catching unhandled exception on separate threads
  25. Is this a bad practice to catch a non-specific exception such as System.Exception? Why?
  26. try catch finally question
  27. What is ApplicationException for in .NET?
  28. Show line number in exception handling
  29. Getting Cross-thread operation not valid [duplicate]
  30. How to log all thrown exceptions?

Leave a Comment