How to capture unhandled exceptions on Windows Services?

.net exception-handling windows-services unhandled-exception
Jader Dias picture Jader Dias · Feb 25, 2011 · Viewed 7.7k times · Source

I use AppDomain.UnhandledException Event to capture unhandled exceptions on WPF, Console and WinForms apps.

But the same code isn't working on Windows Services. What should I do?

Answer

Chris Dickson picture Chris Dickson · Feb 25, 2011

See my answer added to the linked SO question.

There are a number of places in your service code where a thrown exception will not be "unhandled" even if you don't handle it, because the base class does so before it reaches the AppDomain's default handler.

Related questions

Catch multiple exceptions at once?

It is discouraged to simply catch System.Exception. Instead, only the "known" exceptions should be caught. Now, this sometimes leads to unneccessary repetitive code, for example: try { WebId = new Guid(queryString["web"]); } catch (FormatException) { WebId = Guid.Empty; } catch (OverflowException) { WebId = …

Read More
How using try catch for exception handling is best practice

while maintaining my colleague's code from even someone who claims to be a senior developer, I often see the following code: try { //do something } catch { //Do nothing } or sometimes they write logging information to log files like following try catch …

Read More
Is there a difference between "throw" and "throw ex"?

There are some posts that asks what the difference between those two are already. (why do I have to even mention this...) But my question is different in a way that I am calling "throw ex" in another error god-like …

Read More