I have a windows service that does some intensive work every one minute (actually it is starting a new thread each time in which it syncs to different systems over http). Th
Based on the information that you provided, I would at least, at the minimum, do the following:
AppDomain.CurrentDomain.UnhandledException won't help you - a StackOverflowException being one of them. I believe the CLR will simply just give you a string in this case instead of a stack trace.An example of an often overlooked StackOverflowException is:
private string myString;
public string MyString { get { return MyString; } } //should be myString