A very nice comment tail is growing at the post " Why catch(Exception)/empty is bad " on the CLR team blog . I tend to agree but there are perfectly valid reason's to do a generic catch but with a correct handler, an empty handler is *always...
I just read this article by DigiMortal about List<T>.ForEach and exceptions . His assumption was that if an exception occurs while processing one of the items that the next item would still be processed which is not that case. Maybe he was aware...