So, I'm migrating projects from SlimDX and .NET 3.5, and there are two things that were insanely helpful on that side that I can't seem to find via a search of Answers, the Forum, or the Unity script documentation.
Obviously there are a few custom calls in there, but those are just illustrative; the main thing is what happens in Main. Basically, that lets me get exceptions off the main thread, and off any other threads, and have them be logged in a super useful format. I'm even packaging the debug symbols along with, so it gives me a line number along with any errors. For public betas, that is super useful in particular.
I know that Unity has the log under the _Data folder in windows (and something comparable on OSX), but that doesn't seem to log everything, it doesn't let me log custom messages to my knowledge, and it gets cleared out every time the player starts another game. I love that that Unity log exists, and it's not like I want to turn that off or anything, but I'd also love to be able to additionally do something more like the above in addition.
Have you reviewed Application.RegisterLogCallback ? While I haven't tested it myself, it would seem to be exactly what you need - you can use it to register your own callback function and then from it log by whatever method you desire (say, log4net).
answered Jun 21 '10 at 03:20 PM
Regarding overflows and underflows:
You can use the checked and unchecked keywords to change the behaviour at a block level. It may not be the same as application level settings, but it's pretty much the only way it'll work with unity
About the exception handling:
You may be able to get away with adding your functions to the same events that you do in main. This won't catch native exceptions though, and not much can be done about that
You can then pump your exceptions to your own log file (System.IO.File.* perhaps) if you prefer not to use the output.log provided by Unity
answered Jun 21 '10 at 03:18 PM