1) The event viewer itself can save events to a file. You can open the event log on another computer. Monitors are generally written to keep an eye on the event log, so this could leverage any already in place or planned on monitoring infrastructure. WMI is a standard.
There isn't really any right answer. For a shop with it's own IT that is rolling out a custom app to a limited number of users, the event log may be the way to go. It's a good option for servers in an enterprise system. -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Franklin Gray Sent: Friday, September 16, 2005 10:03 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Best way to handle errors in .net 1) Great for when you can get to the machine or have power users who can send you the event log. Does anybody know if there is a way to program the saving of a windows event log to a file? 2) Simple approach....works well when using a tracer. 3) Overkill and overhead....specially if you combine errors with bebugging and tracing. 4) The DB connection can be the error....then what? =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
