J
james.igoe
No so much a question, but looking for feedback on building ne's own
logging features:
Being new to DotNET, I wanted to build a website properly from the
ground up, so one of the first things I created was a system logger
class and a related table. The class can be included in an code
behind module, and then various methods can be invoked, depending on
the logging values required. I have methods for generic logging, used
for page hits, in which I collect browser, page name and IP info, as
well as error logging methods, which allow me to collect error values
and stack trace information.
I've seen the packages, and wondering what I lose out on by not using
them.
logging features:
Being new to DotNET, I wanted to build a website properly from the
ground up, so one of the first things I created was a system logger
class and a related table. The class can be included in an code
behind module, and then various methods can be invoked, depending on
the logging values required. I have methods for generic logging, used
for page hits, in which I collect browser, page name and IP info, as
well as error logging methods, which allow me to collect error values
and stack trace information.
I've seen the packages, and wondering what I lose out on by not using
them.