Application log files. . .

[Joe Mamma]

I have seen a few people tring to reinvent the wheel by creating an application log file and then having problems with accessing the file, keeping the fiole synced between instances, etc. . .

 

Don't rebuild the wheel, just do the following:

 

1. Drop an EventLog component from the components tab on to your form/page and :

 

windows -

eventLog1.Source = this.Name;
eventLog1.Log = Application.ProductName;
eventLog1.WriteEntry("Something Happened", System.Diagnostics.EventLogEntryType.Information,0);

or

ASP.NET

eventLog1.Source = this.Name;
eventLog1.Log = HttpContext.Current.Request.ApplicationPath;
eventLog1.WriteEntry("Something Happened", System.Diagnostics.EventLogEntryType.Information,0);

[mskeel]

I am all for code reuse, but what would the advantage to using this component be over something like, say, the Apache Logging Services? It seems like all of your logs will be locked into the windows event logging stuff. Will normal users be able to use and view these logs?

 

Opinions or advice from anyone who has actually used these classes before?

[IngisKahn]

I use the Enterprise Library myself (at least for .NET 1.1 projects).