Wednesday, May 14, 2003 2:58 PM szurgot

ASP.NET Trace functionality & Remote Errors

Suggestion for ASP.NET 2.0:

ASP.NET Trace.Write/Warn and RemoteError functionality is wonderful and all, but there really needs to be a way to view this information without having to log directly into the console, or opening up the views to everybody. IE: a special ip exception list, where anybody on this list gets directly to the trace, or a special NTLM login list that applies to trace.axd. It's frustrating to pull out Terminal Services just to check a quick error :(

Comments

# re: ASP.NET Trace functionality & Remote Errors

Wednesday, May 14, 2003 1:05 PM by Matt Berther

Chris:

Have you looked at implementing your own TraceListener object that could, for example, write trace methods to a sql server database or email the trace reports to you?

The abstract class that you would derive from is documented at MSDN.

# re: ASP.NET Trace functionality & Remote Errors

Wednesday, May 14, 2003 1:17 PM by Chris Szurgot

Thing is, that's not for Context.Trace.Write, that's for System.Diagnostics.Trace.Write(Line), etc... That TraceListener wouldn't even capture those Trace.Write/Warn commands. Plus, you lose all the ancillary information like Headers/Cookies/Form/etc...

# re: ASP.NET Trace functionality & Remote Errors

Wednesday, May 14, 2003 3:15 PM by Jim Geurts

Have a look at log4net (http://sourceforge.net/projects/log4net/).