VB6 Equivalent

[Phil Hunt]

Is there a .NET #C equivalent of VB6 "On Error Resume Next".

[Tom Shelton]

On 2008-05-22, Phil Hunt <aa*@aaa.comwrote:

Is there a .NET #C equivalent of VB6 "On Error Resume Next".

Not really, the closest would be that you would have to enclose every
line in a try catch statement...

try
{
// one line of code
}
catch {}

try
{
// next line of code
}
catch {}

....
--
Tom Shelton

[sloan]

The #1 thing you can do with a VB6 mentality of exception handling in DotNet
is

1. Put it in a brown paper bag.
2. Take it to someone's house you don't like.
3. Set it on fire.
4. Run away from it as fast as you can.
...

I'm not trying to be mean, but rather FIRM about it.

Check here:
http://blogs.msdn.com/kcwalina/archi...16/396787.aspx
If you're using "resume next" in your VB.NET code, then stop doing it. Just
because you ~can~ doesn't mean you ~should~.

...

Good luck.



"Phil Hunt" <aa*@aaa.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...

Is there a .NET #C equivalent of VB6 "On Error Resume Next".

[Tom Shelton]

On 2008-05-22, sloan <sl***@ipass.netwrote:

>
The #1 thing you can do with a VB6 mentality of exception handling in DotNet
is

1. Put it in a brown paper bag.
2. Take it to someone's house you don't like.
3. Set it on fire.
4. Run away from it as fast as you can.
..

LOL... So true.

--
Tom Shelton

[Phil Hunt]

Well, there should be a way available to disable it no matter how good it
is.
"Tom Shelton" <to*********@YOUKNOWTHEDRILLcomcast.netwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...

On 2008-05-22, sloan <sl***@ipass.netwrote:

>>
The #1 thing you can do with a VB6 mentality of exception handling in
DotNet
is

1. Put it in a brown paper bag.
2. Take it to someone's house you don't like.
3. Set it on fire.
4. Run away from it as fast as you can.
..

LOL... So true.

--
Tom Shelton

[sloan]

//quote
Well, there should be a way available to disable it no matter how good it
is.
//end quote
Huh?

"Phil Hunt" <aa*@aaa.comwrote in message
news:u1**************@TK2MSFTNGP03.phx.gbl...

Well, there should be a way available to disable it no matter how good it
is.
"Tom Shelton" <to*********@YOUKNOWTHEDRILLcomcast.netwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...

>On 2008-05-22, sloan <sl***@ipass.netwrote:

>>>
The #1 thing you can do with a VB6 mentality of exception handling in
DotNet
is

1. Put it in a brown paper bag.
2. Take it to someone's house you don't like.
3. Set it on fire.
4. Run away from it as fast as you can.
..

LOL... So true.

--
Tom Shelton

[Jon Skeet [C# MVP]]

Phil Hunt <aa*@aaa.comwrote:

Well, there should be a way available to disable it no matter how good it
is.

What, exception handling? No, not really. Exceptions are thrown for a
purpose. The closest you can come to ignoring them is to explicitly put
a try/catch block around each statement. This is really painful, for a
very good reason - if something goes wrong, you almost *never* just
want to ignore it and carry on with the very next statement.

--
Jon Skeet - <sk***@pobox.com>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com

[Scott M.]

Agreed. I always thought of On Error Resume Next as "Close your eyes and
cover your ears and pretend everything is ok, when it isn't".
"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:MP*********************@msnews.microsoft.com. ..

Phil Hunt <aa*@aaa.comwrote:

>Well, there should be a way available to disable it no matter how good it
is.

What, exception handling? No, not really. Exceptions are thrown for a
purpose. The closest you can come to ignoring them is to explicitly put
a try/catch block around each statement. This is really painful, for a
very good reason - if something goes wrong, you almost *never* just
want to ignore it and carry on with the very next statement.

--
Jon Skeet - <sk***@pobox.com>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com