Tilted Forum Project Discussion Community - View Single Post

Stompy · 04-28-2004, 03:31 PM

I have an asp.net application that references a DLL I've created. I wanted to test the speed of the application as a whole so I added an argument to each class' constructor that takes in the TraceContext arg.

Now, within my code in the DLL, I have Traces usually around each major function.

If I disable Tracing via the web.config, will leaving those Trace.Write methods in the code slow things down, or does it just disregard them?

I figure this is a good way to test the performance of my apps as I can leave the trace code inside the DLL and just enable tracing whenever I want to see overall page performance, but I'm unsure of the effects of leaving Trace code within my DLLs.

04-28-2004, 03:31 PM	#1 (permalink)
Stompy Banned from being Banned Location: Donkey	ASP.net and Page/Application Tracing I have an asp.net application that references a DLL I've created. I wanted to test the speed of the application as a whole so I added an argument to each class' constructor that takes in the TraceContext arg. Now, within my code in the DLL, I have Traces usually around each major function. If I disable Tracing via the web.config, will leaving those Trace.Write methods in the code slow things down, or does it just disregard them? I figure this is a good way to test the performance of my apps as I can leave the trace code inside the DLL and just enable tracing whenever I want to see overall page performance, but I'm unsure of the effects of leaving Trace code within my DLLs. __________________ I love lamp.