By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,369 Members | 1,147 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,369 IT Pros & Developers. It's quick & easy.

efficiently using .net Tracing

P: n/a
Hi all,

I know tht we can do tracing in two ways.one in application level and the
other is at Page level.
I am able to see the details of trace either on the page itself or
.../trace.axd page.
I want to use maximum out of the available trace details .
or
let me put it like this....
tell me the actual scenario's where these trace details will be use ful and
how to use them.

Advanced Thanks,
deepu
Nov 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a


"deepukutty" wrote:
Hi all,

I know tht we can do tracing in two ways.one in application level and the
other is at Page level.
I am able to see the details of trace either on the page itself or
../trace.axd page.
I want to use maximum out of the available trace details .
or
let me put it like this....
tell me the actual scenario's where these trace details will be use ful and
how to use them.

Advanced Thanks,
deepu


Hi DeepuKutty,

What is Tracing?
==========
Tracing is an activity of recording the diagnostic information related to a
specific web page that is being executed on the web server. In this
discussion we will consider ASP.NET related tracing technique.

Need of Tracing
==========
When the application are in development stage, developers can use in-built
debuggers for troubleshooting, but in the production environment, using
debuggers becomes a huge task for administrators considering the security and
related issues. To debug Classic ASP applications, we were having no
mechanism to track the execution flow of ASP pages. Thanks to .NET !!. Using
..NET technology we can trace the flow with really less efforts. To collect
the statistics like execution time, contents of certain object,
“response.write” was the only way in classic ASP. Using trace we are now able
to view the HTTP headers, session state and likewise information on the trace
output. Also, we have flexibility to add our own contents in the trace output.

Tracing Methods
On the Page
When this method is used, the trace output is displayed on the page that is
executed.

Out of Page
In this method, the tracing results are not displayed on the page but these
are stored on the web server and in the root folder of the application in a
file named as “trace.axd”. After execution of the pages, this file can be
viewed on the browser. For example http://yourApplicationroot/trace.axd.

How Do I trace?
The tracing can be enabled at two scopes:

Page Level
Application Level

For further Reading
**************
ASP.NET Trace
==========
http://msdn.microsoft.com/library/de...ctionality.asp

Reading Trace Information
=================
http://msdn.microsoft.com/library/de...ngtracelog.asp

Enabling Application-Level Tracing
======================
http://msdn.microsoft.com/library/de...veltracing.asp

Writing Trace Messages
===============
http://msdn.microsoft.com/library/de...totracelog.asp

Enabling Tracing for a Page
==================
http://msdn.microsoft.com/library/de...agesonpage.asp

http://www.codeproject.com/aspnet/Tracing_Explained.asp

bye
Venkat_KL
Nov 19 '05 #2

P: n/a
Hi DeepuKutty,

What is Tracing?
==========
Tracing is an activity of recording the diagnostic information related to a
specific web page that is being executed on the web server. In this
discussion we will consider ASP.NET related tracing technique.

Need of Tracing
==========
When the application are in development stage, developers can use in-built
debuggers for troubleshooting, but in the production environment, using
debuggers becomes a huge task for administrators considering the security and
related issues. To debug Classic ASP applications, we were having no
mechanism to track the execution flow of ASP pages. Thanks to .NET !!. Using
..NET technology we can trace the flow with really less efforts. To collect
the statistics like execution time, contents of certain object,
“response.write” was the only way in classic ASP. Using trace we are now able
to view the HTTP headers, session state and likewise information on the trace
output. Also, we have flexibility to add our own contents in the trace output.

Tracing Methods
On the Page
When this method is used, the trace output is displayed on the page that is
executed.

Out of Page
In this method, the tracing results are not displayed on the page but these
are stored on the web server and in the root folder of the application in a
file named as “trace.axd”. After execution of the pages, this file can be
viewed on the browser. For example http://yourApplicationroot/trace.axd.

How Do I trace?
The tracing can be enabled at two scopes:

Page Level
Application Level

For further Reading
**************
ASP.NET Trace
==========
http://msdn.microsoft.com/library/de...ctionality.asp

Reading Trace Information
=================
http://msdn.microsoft.com/library/de...ngtracelog.asp

Enabling Application-Level Tracing
======================
http://msdn.microsoft.com/library/de...veltracing.asp

Writing Trace Messages
===============
http://msdn.microsoft.com/library/de...totracelog.asp

Enabling Tracing for a Page
==================
http://msdn.microsoft.com/library/de...agesonpage.asp

http://www.codeproject.com/aspnet/Tracing_Explained.asp

bye
Venkat_KL
Nov 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.