Library code snippets
Debug ASP.NET pages using Tracing
In Classic ASP one might debug some code using VB Script:
Response.Write strSQL
Response.End()
and the comment/uncomment the code accordingly. This was a bit of a pain during the development process. In ASP.NET, one can use the Trace feature which simplifies matters somewhat. Page-level tracing can be set in the Page directive on the ASPX page:
<%@ Page Language="c#" Trace="true"%>
and in the code one could use:
string strSQL="select * from " + Table + " " + WhereClause + " order by " + OrderingColumn;
Trace.Write("SQL",strSQL);
When the page is run in the browser, you'll see:
So, you'd be able to see the SQL that is executed. By using Trace.Warn instead of Trace.Write, the line would be highlighted in Red. When the application is deployed, you'd simply disable tracing by setting the Trace attribute to false. If you have many pages that you wish to trace, then it may be more viable to set the tracing in your web.config file:
<system.web>
<trace enabled="true" requestLimit="20" pageOutput="true" traceMode="SortByCategory" localOnly="true" />
</system.web>
So, you can easily enable/disable tracing as required.
Related articles
Related discussion
-
sharepoint calendar web part with events from sql table
by tukubapi2207 (1 replies)
-
Using FedEx Web Service to Calculcate Shipping Cost
by bhora123 (4 replies)
-
Very Urgent regarding deleting the images from a folder
by rameshbandi (2 replies)
-
Dynamically Generating PDFs in .NET
by nike12 (10 replies)
-
New style of Javascript used in extenders.
by mittalpa (0 replies)
Related podcasts
-
StackOverflow uses ASP.NET MVC - Jeff Atwood and his technical team
Scott chats with Jeff Atwood of CodingHorror.com and most recently, StackOverflow.com. Jeff and Joel Spolsky and their technical team have created a new class of application using ASP.NET MVC. What works, what doesn't, and how did it all go down?
This thread is for discussions of Debug ASP.NET pages using Tracing.