Good catch, Tarun. I could swear during the 1.0 days the request limit
was how big the "stack" of trace information was, that is it did not
disable but kept around the most recent X traces.
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Mon, 7 Feb 2005 20:53:02 -0800, Tarun Upadhyaya <t a r u n u p a d
h y a y a @ y a h o o . c o . i n> wrote:
Hi,
There is a requestLimit attribute of the trace element in the web.config
file that
Specifies the number of trace requests to store on the server. The default
is 10. If the limit is reached, trace is automatically disabled.
I think you should try increasing the count and cross check it whether it
disappears after page(s) gets displayed that no of times.
Hope that helps
"Dabbler" wrote:
Thanks for your reply.
No the tracing disappears on subsequent pages. If I reload the original page
the trace info is missing. I have application trace turned on in web.config.
I do not have Trace.Write statements in the subsequent pages. If I reset
everything (reset state server, clear internet cache and cookies) the
application begins tracing again.
Michael
"Scott Allen" wrote:
> Is it the exact same pages that suddenly have no tracing information?
> Is the Trace attribute in any of the ASPX pages that do not show
> tracing?
>
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/
>
> On Mon, 7 Feb 2005 02:39:02 -0800, "Dabbler"
> <Da*****@discussions.microsoft.com> wrote:
>
> >When I first start up an ASP.NET application with tracing enabled in
> >web.config the first few pages show trace at bottom of the page but then at
> >some point the pages return to normal with no trace information displayed.
> >
> >Can anyone tell me what might be causing the Trace to turn off?
> >
> >Thanks for any help with this
> >
> >.NET 1.1 running on localhost
>
>
