Continue Code after Exception

Question

Hi, i would like to know if there is a Way that when an exception is thrown to let the program continue aftare the exception was thronw for example

 try 

      line 1
      line 2
      line 3
      line 4 ( here the exception is throw and jumps to the catch)
      line 5  <-- i would like the program to continue its execution after loggin the error
      line 6  

   catch ex as exception

       log(ex.tostring)

    end try

Thanks for any comments

Answer 1

VB.net does not support this type of construct. Once the exception unwinds the stack, it can't be unwound back again. Some languages do permit you to resume the exception, but they require more sophisticated stack management – essentially coroutines.

Answer 2

try 
  line 1
catch ex as exception
   log(ex.tostring)
end try
try
  line 2
catch ex as exception
   log(ex.tostring)
end try
try
  line 3
catch ex as exception
   log(ex.tostring)
end try
try
  line 4 ( here the exception is throw and jumps to the catch)
catch ex as exception
   log(ex.tostring)
end try
try
  line 5  <-- i would like the program to continue its execution after loggin the error
catch ex as exception
   log(ex.tostring)
end try
try
  line 6  
catch ex as exception
end try

Answer 3

On Error Resume Next is still available in VB.NET, but at the mutual exclusion of structured exception handling Your other option seems to be separate Try..Catch around each statement

But IMHO sweeping exceptions isn't a great strategy - what is causing line 4 to cause an exception?

Answer 4

If you're doing something that you know how to recover from or that isn't vital, you're supposed to wrap just that line in the try/catch with a specific catch. e.g.

try

  line 1
  line 2
  line 3
  Try
     line 4 ( here the exception is throw and jumps to the catch)
  Catch iox as IOException ' or whatever type is being thrown
     'log it
  End Try
  line 5  <-- i would like the program to continue its execution after loggin the error
  line 6  

catch ex as exception

   log(ex.tostring)

end try

Answer 5

If I am not mistaken the "Best Practices for Handling Exceptions" says if you can check for an error that will likely occur then check for that condition. If you can check for dbnull then do so.