"on error goto" or "try catch"

[DraguVaso]

Hi,

As a former VB-programmer I'm used to the "on error goto"-errorhandling. I
see that in actually all the VB.NET-samples I can fin people use the "Try -
catch"-errorhandling.

Which of the two is the best? Are there good reasons to use the Try-Catch?
Will the "on error goto" disapear in the future? Are there any logical
reasons to use trey-catch? Is it 'better' programming? etc etc :-)

I'm jsut more comfortable with the "on error goto", mostly because I'm used
to it I guess. Any help or reflectiosn regarding this subject would be nice!

Thanks in advance!

[Cor]

Hi Dragu,

If you are used to the possibilties from the

Try
Catch (multiples
End Try
Finally

And the nesting posibilities from that, you would not believe you could do
it with the "on error goto"

I hope this gives an idea?

Cor

As a former VB-programmer I'm used to the "on error goto"-errorhandling. I
see that in actually all the VB.NET-samples I can fin people use the "Try - catch"-errorhandling.

Which of the two is the best? Are there good reasons to use the Try-Catch?
Will the "on error goto" disapear in the future? Are there any logical
reasons to use trey-catch? Is it 'better' programming? etc etc :-)

I'm jsut more comfortable with the "on error goto", mostly because I'm used to it I guess. Any help or reflectiosn regarding this subject would be nice!

[Valeria]

Hi,
I was a VB-programmer to and I was used to on error but now Try .. catch is
better.
With this statement you can catch all different types of exceptions and
perform a specific action for each one.
I hope this will be usefull for you
Regards
Valeria

"DraguVaso" <pi**********@h otmail.com> ha scritto nel messaggio
news:3f******** **************@ reader0.news.sk ynet.be...

Hi,

As a former VB-programmer I'm used to the "on error goto"-errorhandling. I
see that in actually all the VB.NET-samples I can fin people use the "Try - catch"-errorhandling.

Which of the two is the best? Are there good reasons to use the Try-Catch?
Will the "on error goto" disapear in the future? Are there any logical
reasons to use trey-catch? Is it 'better' programming? etc etc :-)

I'm jsut more comfortable with the "on error goto", mostly because I'm used to it I guess. Any help or reflectiosn regarding this subject would be nice!
Thanks in advance!

[Herfried K. Wagner [MVP]]

* "Valeria" <va***@tiscali. it> scripsit:

I was a VB-programmer to and I was used to on error but now Try .. catch is
better.

But: _Why_ exactly is it better? It's IMO better in some cases because it
leaves code more compact, but sometimes, for example when impementing a
large algorithm, it's very annoying because it will prevent the reader
from seeing the point of the code.

Just a thought.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Cor]

Hi Herfried,

That discussion was done before you was born

If you have problems with that, start studing Pascal, that was special made
for it.

:-)

Cor

[Herfried K. Wagner [MVP]]

* "Cor" <no*@non.com> scripsit:

That discussion was done before you was born

If you have problems with that, start studing Pascal, that was special made
for it.

LOOOOOOOL.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Valeria]

I think is better only because in this way I can simply specify different
actions for each exception if you want and I never loved on error
statement...
a personal opinion maybe!
Valeria

"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> ha scritto nel
messaggio news:bq******** *****@ID-208219.news.uni-berlin.de...

* "Valeria" <va***@tiscali. it> scripsit:

I was a VB-programmer to and I was used to on error but now Try .. catch is better.

But: _Why_ exactly is it better? It's IMO better in some cases because it
leaves code more compact, but sometimes, for example when impementing a
large algorithm, it's very annoying because it will prevent the reader
from seeing the point of the code.

Just a thought.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Herfried K. Wagner [MVP]]

* "Valeria" <va***@tiscali. it> scripsit:

I think is better only because in this way I can simply specify different
actions for each exception if you want and I never loved on error
statement...
a personal opinion maybe!

\\\
Select Case Err.Number
Case err1, err2
...
Case err3
...
...
End Select
///

IMO, unstructured error handling is a nice feature in some cases, but
generally, structured error handling should be preferred.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[DraguVaso]

Ok!! Thanks everybody!
I got on GotDotNet two nice related articles about it:
http://msdn.microsoft.com/library/en...t_errorhandlin
g.asp

http://msdn.microsoft.com/library/en...hExceptionsErr
orsInVisualBasi cNET.asp
"Valeria" <va***@tiscali. it> wrote in message
news:dk******** *************@n ews1.tin.it...

I think is better only because in this way I can simply specify different
actions for each exception if you want and I never loved on error
statement...
a personal opinion maybe!
Valeria

"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> ha scritto nel
messaggio news:bq******** *****@ID-208219.news.uni-berlin.de...

* "Valeria" <va***@tiscali. it> scripsit:

I was a VB-programmer to and I was used to on error but now Try ..

catch

is better.

But: _Why_ exactly is it better? It's IMO better in some cases because it leaves code more compact, but sometimes, for example when impementing a
large algorithm, it's very annoying because it will prevent the reader
from seeing the point of the code.

Just a thought.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Cor]

Brrrrrrrrrrrrrr rrrrrrrrrr

What is here the difference with a standarized try catch end try finally
solution?

Answer, I have to check the list with errornumbers, and need HKW to give me
a link for that.

\\\
Select Case Err.Number
Case err1, err2
...
Case err3
...
...
End Select
///

Cor