title: Exception handling best practice in a windows service?
body: <p>I am currently writing a windows service that runs entirely in the background and does something every day. My idea is that the service should be very stable so if something goes wrong it should not stop but try it next day again and of course log the exception. Can you suggest me any best practice how to make truly stable windows services? </p>
  
  <p>I have read the article of <a href="http://www.hanselman.com/blog/GoodExceptionManagementRulesOfThumb.aspx" rel="noreferrer">Scott Hanselman of exception handling best practice</a> where he writes that there are only few cases when you should swallow an exception. I think somehow that windows service is one of the few cases, but I would be happy to get some confirmation on that.</p>