swallowed-exceptions

I know it's evil, but I've seen swallowed exceptions in code written by a good programmer. So I'm wondering if this bad practice could have at least one positive point. In other words, it is bad but why do good programmers, on rare occasions, use it? try { //Some code } catch(Exception){} Looking in my own code, I found a place in my logging code where, after failing to write to a file and failing to write to the event log, it swallows the error as there is no place left to report it. That's one example: there aren't many others. Because sometimes the programmer has more knowledge than the

I developed a WPF application and when I launch it in the debug mode I see the following in the output: 'WpfApplication1.vshost.exe' (Managed (v2.0.50727)): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Deployment\2.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll', Symbols loaded. A first chance exception of type 'System.Deployment.Application.InvalidDeploymentException' occurred in System.Deployment.dll Additional information: Application identity is not set. If I use a control from this application in another WPF application, there are 7 such messages in the output. Nevertheless, the application