Z
Zytan
It seems verbose to write
http://blogs.msdn.com/brada/archive/2005/03/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 OutOfMemoryException, and StackOverflowException
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
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/2005/03/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 OutOfMemoryException, and StackOverflowException
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