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.

Hello james,

> 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.

A lot of your own time... ofcourse you can roll your own, but if there is
one that suits your needs, then don't invent the same wheel all over again...
--
Jesse Houwing
jesse.houwing at sogeti.nl

You lose time, as you are re-inventing the wheel, so to speak.

There is nothing wrong with building yourself. And, depending on how well
you like the libraries you can purchase/download, it might be a better
option. So, I am not going to say yes or no on this one.

--
Gregory A. Beamer
MCP: +I, SE, SD, DBA

*********************************************
| Think outside the box!
|
*********************************************
<(E-Mail Removed)> wrote in message
news:f74a7d1e-ee90-4224-b023-(E-Mail Removed)...
>
> 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.