set pageOutput attribute at page level

Last post 05-17-2008 5:24 AM by jchandra. 3 replies.

Sort Posts:

  • set pageOutput attribute at page level

    05-16-2008, 11:25 PM
    • Loading...
    • karang
    • Joined on 04-20-2007, 11:57 AM
    • Gurgaon, India
    • Posts 222

     Hi

     

    If I want to enable page level output for tracing then I can add pageOutput attribute in the <trace> element. Is it possible to set the property pageOutput at page

    Regards

    Karan
     

    For .net,Javascript and Sql server articles and interview question visit


    http://guptakaran21.googlepages.com/mainpage
  • Re: set pageOutput attribute at page level

    05-17-2008, 1:10 AM
    • Loading...
    • jchandra
    • Joined on 05-15-2008, 5:36 AM
    • Jakarta, Indonesia
    • Posts 197

    Have you try adding Trace="true" or Trace="false" at the <%@Page%>? to control individual tracing on each page?

     This will work whether or not pageOutput is turned on in the config or not.  If it is, you can use this to prevent Trace to be output on specific pages.

    Jimmy Chandra
    Blogging at Incoherent Rambling

    Mark this post as Answer if you think it helped you solve the problem.

  • Re: set pageOutput attribute at page level

    05-17-2008, 2:31 AM
    • Loading...
    • karang
    • Joined on 04-20-2007, 11:57 AM
    • Gurgaon, India
    • Posts 222

    Hi Jimmy

    By putting Trace = true I am enabling trace at the page level but I want to enable or disable pageOutput at page level or not. Is it possible?

     

    Regards

    Karan 

    For .net,Javascript and Sql server articles and interview question visit


    http://guptakaran21.googlepages.com/mainpage
  • Re: set pageOutput attribute at page level

    05-17-2008, 5:24 AM
    Answer
    • Loading...
    • jchandra
    • Joined on 05-15-2008, 5:36 AM
    • Jakarta, Indonesia
    • Posts 197

    I am not sure if that's doable. I believe once pageOutput is set to true in the config, the only way to not show it on a specific page is either you set the localOnly to true (but it will still show on the server) or completely turn off tracing for that particular page by doing what I mentioned before (Trace="false").

    One option you can choose is to turn off pageOutput and leave Tracing on in web.config, and then on a different browser (even on a different machine), you can invoke the trace.axd from the root folder of your site / web application and you'll be able to see all the traces coming from any machines that are using your site.

     i.e. http://mywebserver/trace.axd

    For advance ASP.NET tracing and debugging tutorial, watch the screencast in this post by Scott Hanselman.

    Jimmy Chandra
    Blogging at Incoherent Rambling

    Mark this post as Answer if you think it helped you solve the problem.

Page 1 of 1 (4 items)