Or just use realtime debugging in VS.NET
Jeff
"Anders Norås" <an**********@objectware.no> wrote in message
news:69****************************@phx.gbl...
Console.Write line writes to the TextWriter assigned to
the Console.Out property. You can use Console.SetOut to
change this.
The recommended logging method is to use
System.Diagnostics.Debug class for debug messages and
System.Diagnostics.Trace class for general tracing
messages.
The easiest way to see trace messages in an ASP.NET
application is to either set Trace="true" in the Page
directive in your ASPX page to have trace messages
included at the end of the page or configure the trace
element in the system.web section of the web.config file.
Like this:
<trace enabled="true" requestLimit="10"
pageOutput="false" traceMode="SortByTime"
localOnly="true" />
You can see trace messages for the entire application in
by navigating to trace.axd on the root of the application.
Anders Norås - blog:
http://dotnetjunkies.com/weblog/anoras/ -----Original Message-----
In j2ee/JBuilder/WebLogic when you do a
System.err.println(), you can seethe messages in the console that started the server.
When I tried the sametype of thing with VS 2k3 .NET and ASPX, I don't see the
messages. Where dothey go? What is the suggest logging method to use for
debugging and fordevelopment apps?
I broke out the question into two parts cause I'm
looking to find out how todo quick'n'dirty debugging on the fly vs something a
bit more formal anddependable.
Thanks.
.