Since the directory in the example is the applications startup path, when you look for your error log in debug mode, it will appear in the TestProject\bin\Debug folder and a subordinate folder called "Errors".Īfter checking on the directory, the next section checks on the file itself in this case I have named the error log "errlog.txt" so this methods looks for that file and creates it if it does not exist.
#DFS CDMA TOOL ARITHMETIC OPERATION RESULTED IN AN OVERFLOW CODE#
The next section of the code checks for the existence of the directory where the error will be written and if it does not exist, it creates it. Where the subroutine it declared, you will note that it excepts three arguments: The message you wish to record (typically I would use the exception's message here but it could be any string), the stack trace which is the exception's stack trace, and the error's title which could be any string you wish to use as an error entry's title. S1.Write( "StackTrace: " + stkTrace + vbCrLf) StreamWriter s1 = new StreamWriter (fs1) ReadWrite) įileStream fs1 = new FileStream (Application.StartupPath + "\\Errors\\errlog.txt", FileMode. CreateDirectory(Application.StartupPath + "\\Errors\\" ) įileStream fs = new FileStream (Application.StartupPath + "\\Errors\\errlog.txt", FileMode. Exists(Application.StartupPath + "\\Errors\\" ))) Public void WriteToErrorLog( string msg, string stkTrace, string title) stkTrace - stack trace from error message PARAMETERS: msg - message to be written to error file PURPOSE: Open or create an error log and submit error message
Looking on, the rest of the code looks like this: (modified to fit on this page) Further both this class and the EventLogger.cs class could be written as modules which would eliminate the need to instance the class if you prefer that approach. This, in C#, does not really need to be explicitly stated, however, it would be a nice improvement to add an additional constructor to allow you pass in all of the required arguments in the initialization and to create the log entry without subsequently evoking the classes' method used to write to the error log. You will note that this is a class rather than a module and for that reason it has an empty default constructor. The class is again pretty trivial, the imports at the beginning of the class are needed to read and write to a file, and to derive information about the application (namely its path). At the beginning you will see the following: Open up the ErrorLogger.cs class and examine the code. As you can probably guess, ErrorLogger.cs creates and writes to an error log while EventLogger.cs writes to the system event log. If you take a look at the class library project, you will note that it contains two classes: ErrorLogger.cs and EventLogger.cs. Unzip the attached project in it you will find a class library project entitled, "EventsAndErrors" and a separate test project that subsequently uses the EventsAndErrors class library.
Event logging is probably a better alternative to error logging in fully fielded systems. Such log entries are categorized and made visible through the system event viewer console. The event log is a system construct used to capture different types of information regarding the operational status of applications running on that system. The error log class included with this example creates time stamped entries showing the exact method and line of code where the error occurred as well as the error message generated.
Error logs are most useful during an early or beta release of a product where you have a limited set of users and you have an opportunity to capture the error logs back from these users. This article describes an approach to writing to a custom error log and to writing events into the system event log.Įrror logs are a useful method for collecting all error data generated by an application this often includes trapped errors that you may not need to or care to show to the end user.
0 kommentar(er)
