jsampsonPC wrote:Well, I'm about to start developing an admin section to an internal-web-app we use in our office and I want to add a logging class to it to track wo does what, when, and what the result was...etc.
user Michael Smith attempted to access Customer Records for Smith, John at 12:45pm on Wednesday, November 28, 2007. Failed.
user Jonathan Sampson accessed Customer Records for Smith, John at 12:53pm on Wednesday, November 28, 2007. Success.
user Jonathan Sampson deactivated Customer Account for Smith, John at 1:28pm on Wednesday, November 28, 2007. Success.
That sort of thing, of course the values would be pulled from the database.
So I'm curious to hear how you guys have designed your classes in the past. Do you have enumerated lists within your class to manage your event-types ("Accessed an account", "Removed an account", "Created an account")
I've never really designed a class like this before, so I'm coming from a completely blank-slate...which I guess is cool
well you can do several kinds of logging and if you need a really good traking then IMHO you should impliment multiple logs.
for example if you use the asp.net membership system you can log asp.net events to the event log and to a database table.
this can for example log login errors and application exceptions...
more later on sql logging.