5

i want to know do finally block still execute in exception handling even if there is no matching catch block for the try block and if not then what happens? Also i want to now system exception and application difference

VoteyDisciple
  • 37,319
  • 5
  • 97
  • 97
NoviceToDotNet
  • 10,387
  • 36
  • 112
  • 166

2 Answers2

13

Yes, you do not need a catch block at all. The finally block always executes.

As to the difference between System.Exception and System.ApplicationException: Exception is the base class for all exceptions; ApplicationException should be used when a non-fatal application error occurs. See the MSDN documentation.

Also see best practices for handling exceptions.

Shaul Behr
  • 36,951
  • 69
  • 249
  • 387
  • you mean after running the finally block the exception will be thrown and the program will terminate? (when there is no matching catch block) – NoviceToDotNet Oct 17 '10 at 15:25
  • Well, yes and no. The exception will be thrown, but there could be another try-catch block surrounding the call to this one, in which case the higher level try-catch will catch this exception. – Shaul Behr Oct 17 '10 at 16:21
  • 2
    As an aside, don't use `ApplicationException`. It is deprecated. Use an appropriate exception derived from System.Exception (or derive your own) instead. – mtreit Oct 17 '10 at 16:42
4

As others mentioned finally will run even if there is no catch block. This supports Java's try finally pattern (which can be achieved using IDisposable and using).

One exception (see what I did there?) is when a StackOverflowException is thrown in which case the finally block will not run (nor would a catch if one were present).

The finally block runs after the try block completes (either cleanly or by throwing an exception) as you would expect from its location in the code.

Community
  • 1
  • 1
Motti
  • 110,860
  • 49
  • 189
  • 262