System.Overflow Exception - int32 is too large or small

I need a little advice.

I've got windows service that runs at night. In my development environment, it runs without exception, but when I running it "installed on other machines", when I come in the morning, I'm welcomed with a System.Overflow exception that says that I've set an int32 to a value that is too large or small.

I've carefully combed the service's c# code, and I have try/catch statements around everything, that should catch any error and write it to a log without completely stopping my service 开发者_C百科with this overflow exception. But still, it occurs and stops the service.

I'd appreciate any conceptual advice on how to pin point what's causing an error such as this.

---

The problem with adding try/catch blocks throughout your code is it's easy to miss a place and hence not log the exception. A much more robust approach is to use the value AppDomain.UnhandledException. This will fire for any exception which is not handled within the current AppDomain. You can hook into this to write to your log file and hopefully get a better idea at where the error is coming form

AppDomain.CurrentDomain.UnhandledException += OnUnhandledException;

...

void OnUnhandledException(object sender, UnhandledExceptionEventArgs e) {
 // Log the exception here
}

---

• You must have missed an instance of try/catch or you have an error in your error handler or it would be handled.
• In windows you can setup your service to restart if it ends unexpected manner.

---

First, let me tell you that overflow/underflow can be disabled, by opening project properties, selecting "Build" (from the left menu), and then "Advanced...".

By the way, I do it all the time, because it adds overhead, which I don't want in my scientific applications. Manually, then I control things.

But that does not solve the issues... It just hides the "problem", if it is a problem.

If you only care to check about a zero/non zero condition, somewhere in your code, disabling overflow at project settings solves the problem, because even when an overflow occurs you get a nonzero value, and your service continues without problems.

---

Also, for WinForms applications:

http://msdn.microsoft.com/en-us/library/system.windows.forms.application.threadexception.aspx

And WPF:

http://msdn.microsoft.com/en-us/library/system.windows.application.dispatcherunhandledexception.aspx

To get visibility of exceptions on UI threads, since they're not forwarded to AppDomain.CurrentDomain.UnhandledException.