During software development, testing and even when it is in the production environment, error reporting and tracing are considered to be the most valuable requirement, since it eases the process of troubleshooting and bug fixing.
There are multiple repositories where you can log, event log, database, file, etc.
In my article, I will be introducing a custom component responsible for logging into a file.
Before starting with this article, you should be familiar with the .NET Framework, C# and IO processing in C#.
Using the Code
In this article, you will find three main classes:
FileTracer is where the actual logging takes place. The class is responsible for creating the logging directory if it does not exist. The class logs into the log file according to the trace level supplied, and keeps track to the file size. If it exceeds the maximum file size, it will archive the file and create a new one.
FileTracerHelper can be described as the Facade for the client, which will expose all tracer functionality.
TraceEnterExit is a disposable class responsible for reporting entering and exiting functions.
Logging Format will be ([|] Thread | Date Time | Level | Location | Data [-]) where:
- Thread is the execution thread
- Date Time is execution time
- Level is (Information, Warning or error)
- Location is function name
- Data is user logged data
public static void Information(string location, string message)
FileTracer.Write(TraceLevel.Info, location, message);
Like the above, there is a
public function for logging warnings and errors, and can be used as follows:
private void CalculateNumbers()
using (TraceEnterExit tee = new TraceEnterExit("CalculateNumbers"))
int counter = 0;
int userCounter = Convert.ToInt32(txtSucessfullLogging.Text);
for (int i = 0; i < 5; i++)
( "CalculateNumbers", "Counter after processing = " + counter.ToString());
TraceEnterExit, you will keep track of whether the function was called and finished or not, logging information if needed and logging errors for troubleshooting.
Points of Interest
You can change the logging format by changing in the
FileTracer class -> Write function by redefining the string builder.