title: .NET Production Debugging
body: <p>I've had a Windows app in production for a while now, and have it set up to send us error reports when it throws exceptions. Most of these are fairly descriptive and help me find the problem very quickly (I use the MS Application Exception Block). </p>
  
  <p>On a few occasions I have reports that are issues that I can't reproduce, and seem to only happen on a few client machines. </p>
  
  <p>I don't have physical access to these client machines, what are some strategies I can use for debugging? Would it be better to build some tracing into the code, or are there some other alternatives?</p>
  
  <p>Thank you.</p>
  
  <p>Edit: I should have been more clear: The error reports that I get do have the stack trace, but since it's production code, it doesn't indicate the exact line that caused the exception, just the method in which it was thrown.</p>