Click here to Skip to main content
Click here to Skip to main content
Add your own
alternative version

Step by Step Guide to Trace the ASP.NET Application for Beginners

, 19 May 2010
Explains the step by step approach to trace the ASP.NET application
TraceDemo.zip
TraceDemo
TraceDemo
App_Data
TraceDB.mdf
TraceDB_log.LDF
bin
TraceDemo.dll
TraceDemo.pdb
Properties
TextWriterOutput.log
TraceDemo.csproj.user
TraceDemo.gpState
TraceDemo.suo
<?xml version="1.0"?>

<configuration>

  <appSettings>
    <add key="ConnectionString" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|TraceDB.mdf" />
    <add key="MaximumRequests" value="2" />
  </appSettings>
    <connectionStrings/>
  <system.diagnostics>
    <trace autoflush="true">
      <listeners>
        <add name="WebPageTraceListener"
            type="System.Web.WebPageTraceListener, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
        <add name="DBTL" type="TraceDemo.DatabaseTraceListener,
                                                TraceDemo"/>
        <add name="myListener"
         type="System.Diagnostics.TextWriterTraceListener"
         initializeData="TextWriterOutput.log" />
        
      </listeners>
    </trace>    
  </system.diagnostics>
    <system.web>
      <trace
        pageOutput="true"
        enabled="true" 
        localOnly="false"
        requestLimit="10"
        mostRecent="true"
        traceMode="SortByTime"
        />
        <!-- 
            Set compilation debug="true" to insert debugging 
            symbols into the compiled page. Because this 
            affects performance, set this value to true only 
            during development.
        -->
        <compilation debug="true" />
        <!--
            The <authentication> section enables configuration 
            of the security authentication mode used by 
            ASP.NET to identify an incoming user. 
        -->
        <authentication mode="Windows" />
        <!--
            The <customErrors> section enables configuration 
            of what to do if/when an unhandled error occurs 
            during the execution of a request. Specifically, 
            it enables developers to configure html error pages 
            to be displayed in place of a error stack trace.

        <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />
        </customErrors>
        -->
      <customErrors mode="Off"></customErrors>
    </system.web>
  
</configuration>

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Jitendra Zaa
Software Developer (Senior) GlobalLogic
India India
From a Nagpur City of Maharashtra currently working as Sr. Software Engineer at GlobalLogic India pvt. Limited.
He has nearly 3 years experience and worked in many technologies like JAVA, PHP, JSP, Struts, Hibernate.
Currently working on .Net technology with C#, ASP and telerik controls.
Also has experience in cloud computing including salesforce.com.
you can reach him at ilovenagpur@gmail.com
Blog:http://www.shivasoft.in/blog

| Advertise | Privacy | Mobile
Web04 | 2.8.140721.1 | Last Updated 19 May 2010
Article Copyright 2010 by Jitendra Zaa
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid