Code after Try...Catch Block

[Simon]

I was of the impression that code placed after a
Try...Catch block was only executed if there was no
exception thrown.

I've got some VB.net code as part of a Windows form that
executes even when an exception is thrown - it behaves as
if the code is part of a finally block.

Looking through all the documentation and MSDN articles,
it seems that none of the examples contain code placed
after a try...catch block nor explain the ramifications
of doing so.

Any ideas? Perhaps I should just move the code into the
try block after the code likely to cause an error.

Simon.

[Robin Tucker]

If you don't want it executed after an exception, put it into the try/catch
block. I don't know if code execution after the "finally" block is well
defined or not. I guess it depends on the exception.

try

do.causeanexcep tion ()
do.thiswontexec uteifanexceptio nfired ()

catch ( Ex as Exception )
do.therewasanex ception()
finally
do.thisisalways executed ()
end try

"Simon" <us****@simonea st.NOSPAMnet> wrote in message
news:0b******** *************** *****@phx.gbl.. .

I was of the impression that code placed after a
Try...Catch block was only executed if there was no
exception thrown.

I've got some VB.net code as part of a Windows form that
executes even when an exception is thrown - it behaves as
if the code is part of a finally block.

Looking through all the documentation and MSDN articles,
it seems that none of the examples contain code placed
after a try...catch block nor explain the ramifications
of doing so.

Any ideas? Perhaps I should just move the code into the
try block after the code likely to cause an error.

Simon.

[Jay B. Harlow [MVP - Outlook]]

Simon,
In addition to what Robin stated:

Is your code outside of the try Catch block?

Then yes it will be executed.

' code here will be executed
try

do.causeanexcep tion ()
do.thiswontexec uteifanexceptio nfired ()

catch ( Ex as Exception )
do.therewasanex ception()
finally
do.thisisalways executed ()
end try
' code here will also be executed,
' unless you have a throw in your catch or finally block above.

The code after the Try block will be executed in the above case if
"therewasanexce ption" or "thisisalwaysex ecuted" functions do not raise an
exception. If either of the functions raise an exception, then the code
after the Try block will not be executed.

Hope this helps
Jay

"Simon" <us****@simonea st.NOSPAMnet> wrote in message
news:0b******** *************** *****@phx.gbl.. .

I was of the impression that code placed after a
Try...Catch block was only executed if there was no
exception thrown.

I've got some VB.net code as part of a Windows form that
executes even when an exception is thrown - it behaves as
if the code is part of a finally block.

Looking through all the documentation and MSDN articles,
it seems that none of the examples contain code placed
after a try...catch block nor explain the ramifications
of doing so.

Any ideas? Perhaps I should just move the code into the
try block after the code likely to cause an error.

Simon.

[Cor]

Hi Simon,

I had always the idea that code was executed in a Try........Catc h block,
till the exception was thrown, then went to the Catch block and then to the
Finaly block. And when there is no return or something in that, do the
statement direct after the Finaly block.

That is what it does in my debugger and if it would not be the same in a
real situation I think I would not be happy.

But if I am wrong, please correct me?

Cor

[Armin Zingler]

"Simon" <us****@simonea st.NOSPAMnet> schrieb

I was of the impression that code placed after a
Try...Catch block was only executed if there was no
exception thrown.

I've got some VB.net code as part of a Windows form that
executes even when an exception is thrown - it behaves as
if the code is part of a finally block.

Looking through all the documentation and MSDN articles,
it seems that none of the examples contain code placed
after a try...catch block nor explain the ramifications
of doing so.

Any ideas? Perhaps I should just move the code into the
try block after the code likely to cause an error.

You mean the code after the "End Try"? It is only executed whenever no
exception occured OrElse the occured exception is handled by a catch
statement.
--
Armin

[Tom Spink]

Hi Cor,

Code in a finally block is executed ALWAYS, regardless of Exit
Sub/Function's or Returns. Code after a Try..End Try block is always
executed, unless there is a Exit Sub/Function or Return or another exception
thrown in the finally or catch block.

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

" System.Reflecti on Master "

==== Converting to 2002 ====
Remove inline declarations
"Cor" <no*@non.com> wrote in message
news:eF******** ******@TK2MSFTN GP12.phx.gbl...

Hi Simon,

I had always the idea that code was executed in a Try........Catc h block,
till the exception was thrown, then went to the Catch block and then to the Finaly block. And when there is no return or something in that, do the
statement direct after the Finaly block.

That is what it does in my debugger and if it would not be the same in a
real situation I think I would not be happy.

But if I am wrong, please correct me?

Cor

[Simon]

Thanks Tom and others. That clears up my thinking quite
a bit. So basically code placed after an End Try will
execute unless:
(a) the particular exception wasn't caught
(b) a further exception was thrown in the catch
(c) a return or exit sub was executed.

Whereas a finally block will execute regardless of the
above three conditions, right?

Any corrections on that? Otherwise, thanks for your help.

Simon.

-----Original Message-----
Hi Cor,

Code in a finally block is executed ALWAYS, regardless of ExitSub/Function's or Returns. Code after a Try..End Try block is alwaysexecuted, unless there is a Exit Sub/Function or Return or another exceptionthrown in the finally or catch block.

--
HTH,
-- Tom Spink, Über Geek

[Tom Spink]

That's right. The *only* case where a Finally block won't execute is if the
Try...Catch...E nd Try block isn't entered...

' Some Code
Return
' Some Code
Try
...
Catch Foo As Bar
...
Finally
...
End Try

In this case, Return has been called before the Try...Catch...E nd Try block
has been reached, so finally will not execute.

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

" System.Reflecti on Master "

==== Converting to 2002 ====
Remove inline declarations
"Simon" <us****@simonea st.NOSPAMnet> wrote in message
news:03******** *************** *****@phx.gbl.. .

Thanks Tom and others. That clears up my thinking quite
a bit. So basically code placed after an End Try will
execute unless:
(a) the particular exception wasn't caught
(b) a further exception was thrown in the catch
(c) a return or exit sub was executed.

Whereas a finally block will execute regardless of the
above three conditions, right?

Any corrections on that? Otherwise, thanks for your help.

Simon.

-----Original Message-----
Hi Cor,

Code in a finally block is executed ALWAYS, regardless of ExitSub/Function's or Returns. Code after a Try..End Try block is alwaysexecuted, unless there is a Exit Sub/Function or Return or another exceptionthrown in the finally or catch block.

--
HTH,
-- Tom Spink, Über Geek

[Scott M.]

"Simon" <us****@simonea st.NOSPAMnet> wrote in message
news:03******** *************** *****@phx.gbl.. .

Thanks Tom and others. That clears up my thinking quite
a bit. So basically code placed after an End Try will
execute unless:
(a) the particular exception wasn't caught
(b) a further exception was thrown in the catch

(c) a return or exit sub was executed.

---> If you exit the try...end try, code after the try block will run. But
you are right that if you exit the sub, it won't.
Whereas a finally block will execute regardless of the
above three conditions, right?

Any corrections on that? Otherwise, thanks for your help.

Simon.

-----Original Message-----
Hi Cor,

Code in a finally block is executed ALWAYS, regardless of ExitSub/Function's or Returns. Code after a Try..End Try block is alwaysexecuted, unless there is a Exit Sub/Function or Return or another exceptionthrown in the finally or catch block.

--
HTH,
-- Tom Spink, Über Geek

[Alexandre Moura]

Just being picky, since there is an exception to this rule -
if an "End" instruction is hit, execution stops at that point without
executing any finalize statements.