do you always use try...catch...finally

[reagan123]

i've seen code that uses this alot and then some examples that don't use it at all... any good guidelines of when to use this error checking and when it's not needed?

 

should it be in every method... etc...

 

I did a search but couldn't find such a basic answer.

[IngisKahn]

If you have a function where you think there is a remote possibility that it could throw an execption then 99% of the time you should use it. So the basic answer is yes.

[jmcilhinney]

Every method in the .NET Framework that can throw an exception has that information detailed in the help system. Every method you call that can throw an exception is a candidate for a Try...Catch block. If your code is the only point of access for the objects you are using then in most cases you won't need to use exception handling because if your code is written properly then those exceptional circumstances won't occur. When you should definitely be using exception handling is when you are dealing with objects that can be affected by factors beyond your control, like connecting to a database.

[Joe Mamma]

and, of course, if within a method you instance a class that implements IDisposable, the last thing you should do is call dispose():

 

dim myDisposable as IDisposable = new MyDisposable ()

 

try

' use my disposable

finally

myDisposable.Dispose()

end try

[penfold69]

Of course, that means "The final thing you should do is call dispose" as when I read "The last thing you should do is call dispose" I panicked for a second - I *always* call dispose on disposable objects when I've finished with them!!!

 

B

[reagan123]

thanks everyone!