Exception handling suggestions

[Zytan]

Ok something simple like int.Parse(strin g) can throw these exceptions:
ArgumentNullExc eption, FormatException , OverflowExcepti on

I don't want my program to just crash on an exception, so I must
handle all of them. I don't care about which one happened, except to
write out exception.Messa ge to a log file. It seems verbose to write
out three handlers that all do the same thing. So, I could just catch
Exception. But, is that recommended? It'll catch everything, even
out of memory exceptions.

What do you suggest?

Zytan

[Zytan]

It seems verbose to write

out three handlers that all do the same thing. So, I could just catchException. But, is that recommended? It'll catch everything, even
out of memory exceptions.

http://blogs.msdn.com/brada/archive/...04/385531.aspx
Effective .NET Framework based development: Exception handing and
Memory Management

Brad Abrams states:

"catch (Exception e) is your friend

Myth: Catching Exception is evil
This is motivated by a desire to avoid catching low level exceptions
such as OutOfMemoryExce ption, and StackOverflowEx ception

Do catch every exception you should handle

Don't attempt to catch every exception a method could throw
Its ugly, version brittle, and difficult to test

Catch what you need to handle, let the rest pass"

Zytan

[Todos Menos [MSFT]]

on error goto worked better in my opinion

I mean; using a simple select case statement; you could trap RANGES of
errors

this isn't possible using .NET
'yeah lets just identify every possible error and write it out by
hand'

what a stupid language

LONG LIVE VB6; it's still more popular than VB.net _AND_ C# combined!~

On Mar 30, 7:11 pm, "Zytan" <zytanlith...@g mail.comwrote:

It seems verbose to write
out three handlers that all do the same thing. So, I could just catchException. But, is that recommended? It'll catch everything, even
out of memory exceptions.

http://blogs.msdn.com/brada/archive/...04/385531.aspx
Effective .NET Framework based development: Exception handing and
Memory Management

Brad Abrams states:

"catch (Exception e) is your friend

Myth: Catching Exception is evil
This is motivated by a desire to avoid catching low level exceptions
such as OutOfMemoryExce ption, and StackOverflowEx ception

Do catch every exception you should handle

Don't attempt to catch every exception a method could throw
Its ugly, version brittle, and difficult to test

Catch what you need to handle, let the rest pass"

Zytan