Skip to main content

Using ASP.NET Trace to Explore Web Pages



One can use trace to explore resource usage on each page, and diagnose problems.

Enabling and configuring trace facility:
          Trace facility can be enabled in web.config. It can be also enabled via ASP.NET Web Site Configuration tool.

Following are the ASP.Net trace settings:

Web Site Administration Tool Setting
Web.config
Description
Capture Tracing information
Enabled
Enables tracing.
Display tracing information on individual pages
pageOutput
Displays trace info directly on web page.
Display trace output for
localOnly
If true trace info for only local requests will generated. If false trace info for all requests will be generated.
Select the sort order for trace results
traceMode
By Category or time
Number of trace requests to cache
requestLimit
Sets the quantity of items to hold in the cache.
Select which trace results to cache
mostRecent
Retain the latest or old trace results to meet request Limit.
To enable trace facility in web.config user the following element:
<trace
          enabled = “true”
          requestLimit = “10”
          pageOutput = “false”
          traceMode = “SortByTime”
          localOnly = “true”
          mostRecent = “true”
/>
Viewing the trace data:
          To view the trace output if pageOutput=”false”, navigate to trace.axd.
http://server/application/trace.axd which displays cached results. Note for security one must set pageOutput=”false”.

Trace Results are categorized in to the following sections.

Trace Result Section
Description
Request Details
General details about the request.
Trace Information
Performance info relating page cycles, like request start time & end time.
Control Tree
Displays control info in hierarchy like size.
Session State
All Session variables and their values.
Application State
All application variables and their states.
Request Cookies collection
Cookie list passed to server.
Response Cookies collection
Cookie list passed to the browser.
Header Collection
HTTP Headers sent to the server.
Form Collection
Values that are posted back to the server.
QueryString Collection
Displays Key/value pair of the collection.
Server Variables
Displays all server variables.

Labels:

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...
Post a Comment
Continue Reading »

Asynchronous Execution in ASP.NET

Asynchronous Execution: Two ways either implement IHTTPAsyncHandler interface or in ASP.NET 2.0 set <%@ Page Async=”true” %>. The second option implements IHTTPAsyncHandler interface automatically for the page when parsed or compiled. AddOnPreRenderCompleteAsync ( new BeginEventHandler(BeginTask), new EndEventHandler(EndTask)); AddOnPreRenderCompleteAsync() shoud be called in Page_load. The BeginEventHandler and EndEventHandler are delegates defined as follows: IAsyncResult BeginEventHandler( object sender, EventArgs e, AsyncCallback cb, object state) void EndEventHandler( IAsyncResult ar) AsyncProcess starts and completes between PreRender and PreRenderComplete. Other way to perform Async Task is using AsyncPageTask structure. It also allows multiple tasks to execute simultaneously. void Page_Load (object sender, EventArgs e) { PageAsyncTask task = new PageAsyncTask( new BeginEventHandler(BeginTask), new EndEventH...
Continue Reading »