ASP.Net Trace File

When we enable tracing for a web application where exactly the file or content of the file "Trace.axd" saves?I can't for the life of me understand why this is in this forum. lol|||Well thanks for your EXPLICIT guide!|||No. not this site forum. I'm saying under Sql Server. I'd assume you'd get a lot better results in a more framework oriented forum.

SHEESH!!!

for someone that's requesting help FOR FREE, you're of foul humor. I mean seriously, my life isn't richer and my soul isn't closer to heaven just cuz I help you. It's sheerly by the kindness of my heart and the boredom of insomnia that I'm here even replying to you. So at least be grateful for that.

*clears throat*

Any simpleton would have already tried this

the very first result comes from gotdotnet.
Any other semi-intelligent individual would have seen this one

within that, the set of paragraphs states:
---
In addition to the Page-level Trace funtionality, ASP.NET provides a way to enable trace output for an entire application. Enabling Trace at the application level has the effect of enabling Page-level Trace for every page within that application (provided there is no page-level directive to explicitly disable trace). When application-level tracing is enabled, the ASP.NET runtime also collects several additional statistics, such as the state of the control hierarchy, the contents of session and application state, the form and querystring input values, and other characteristics of request's execution. These statistics are collected for a specified number of requests as determined by the application's configuration file. To enable tracing for an application, place the following in the application's web.config file at the application root directory:

<configuration>
<system.web>
<trace enabled="true"/>
</system.web>
</configuration
Using the above configuration, each page in the application will run its page-level trace statements to be output in the client browser. To access the additional page statistics, request a specially-mapped "trace.axd" URL from the application root. For example, if the URL to your application is http://localhost/myapplication, you would request the URL http://localhost/myapplication/trace.axd to access the trace statistics for that application.
----
kthx bye bye|||I think if you're looking to be richer and want your soul to be closer to heaven , you should'nt be on "Technical Forums" (I think you already know this!!) , you probably used other's ideas , you got other's help (wether it was the kindness of their hearts or anything else) , now you go'n to pass it over (although you can NOT pass it over , too!) , but there's no big deal! once u're helped , once you're helping!
But I appreciate your activity (as any-other-one's)

Yes , I've been "Simpleton" and tried that , though I've read more than this before.

The only statement that might help , is THIS

"To access the additional page statistics, request a specially-mapped "trace.axd" URL from
the application root."

It is mapped , so where's the real version (which that has physical address on the server)?
I knew the mapped URL , but I still don't know where it physically stores on the server!

Thanks again!