Re: reading asp.net trace
- From: "Mark Fitzpatrick" <markfitz@xxxxxxxxxx>
- Date: Thu, 24 May 2007 11:00:22 -0500
Rick,
Usually the best way to use trace is to write your own information
to the trace log. For example Trace.Write("Firing some event","here is some
data from a variable") This will get dumped to the trace log.
Trace's can be excellent in loops as you can output some relevant
data about the loop, such as what iteration you're on (good for spotting
infinite loops) and information from other variables. One of the problems
though with a trace, the entry in the log is not written until the page is
completed executing so you won't have trace info until the page is completed
or terminates due to running too long.
--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006
"Rick Mavrovik" <rick.mavrovik@xxxxxxxxx> wrote in message
news:%23VJzeHfnHHA.4032@xxxxxxxxxxxxxxxxxxxxxxx
hi
one of the pages in my asp.net application is taking very long to load. i
want find out what is causing the problem. its probably ajax.
i am not finding the asp.net trace any useful, i mean i do not know how to
make that trace information useful in diagnosis of this problem..can any
one help me in this regard..
direct to any good resource regarding asp.net trace..
-rick
.
- References:
- reading asp.net trace
- From: Rick Mavrovik
- reading asp.net trace
- Prev by Date: Re: Detailsview Headers
- Next by Date: Re: Ajax web.config error
- Previous by thread: reading asp.net trace
- Next by thread: Re: reading asp.net trace
- Index(es):
Relevant Pages
|
