title: All About Exceptions: What to do and Where to log?
body: <p>My question actually comes in two parts hence the ambiguous title.</p>
  
  <p><strong>Part One</strong></p>
  
  <p>As far as I'm aware, you should never swallow an exception. Not even logging it and forgetting about. In general cases, I try to solve an exception and retry the code - for example, let's say I get a FileNotFound exception.</p>
  
  <p>I prompt the user to check the file exists and try again, offering another file chooser dialog and hoping for the best. Failing attempting to solve the problem I end up notifying the user and logging the exception. I've been told that this isn't the correct thing to do in a catch block, so am I doing it right by attempting to solve the issue?</p>
  
  <p>I can't think what else I should do. I suspect I'm being fed misinformation - I'm a gullable soul.</p>
  
  <p><strong>Part Two</strong></p>
  
  <p>Creating a log in my program directory to log an exception is fine I think, but again I'm being told that exceptions should be written to the windows eventlog. Is this correct? Under what circumstances should you write to the event log?</p>
  
  <p>Silly questions need silly answers.</p>
  
  <p>Edit:
  There is no context to this question other than a general vague domain. My friend and I were blabbering about the right things to do in particular circumstances.</p>