I've observed most developers write their logs to the file system directly
as it doesn't get any more fundamental than that. Some mail themselves an
alert. All the code snippets are out there to be found regardless of where
you want to put it.
In fact I just had a clever thought about logging the exceptions to a blog
which is where the word came from in the first place. Hmmmm not a bad
concept; everything old is new again.
"Fresno Bob" <no****@nospam.comwrote in message
news:%2******************@TK2MSFTNGP03.phx.gbl...
Ha ha :) I was thinking - write to db if you can. Just because a given
line of code generates an SqlException doesn't mean the database can't be
written to.
"HillBilly" <so******@somewhere.comwrote in message
news:%2******************@TK2MSFTNGP03.phx.gbl...
>Now when there is a SqlException :-)
"Fresno Bob" <no****@nospam.comwrote in message
news:Oj****************@TK2MSFTNGP02.phx.gbl...
>>>I was looking at tracing and the way you can write to an axd file. Is
there any way of writing this information to a database but only when the
page errors.