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 »

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...
Continue Reading »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »