Geeks With Blogs
Dennis Bottjer | MVP

I'm sure, like me, you've seen plenty of production web.config files with debug=true set.  Most senior ASP.NET developers will recognize that debug should be set to false for the production build.  However, this small detail is often over looked.  So what does this setting really do and does it have any significant impact on a production site?

When debug is set to true, the following occurs:

  • Pages are not batch compiled.
  • Pages do not time out. When a problem occurs, such as a problem with a Web service call, the Web server may start to queue requests and stop responding.
  • Additional files are generated in the Temporary ASP.NET Files folder.
  • The System.Diagnostics.DebuggableAttribute attribute is added to generated code. This causes the CLR to track extra information about generated code, and it also disables certain optimizations.

Source of Information: http://msdn2.microsoft.com/en-us/library/ms998549.aspx

Posted on Wednesday, October 10, 2007 8:36 AM ASP.NET , .NET , Debugging , Tips-n-Tricks | Back to top


Comments on this post: ASP.NET Debug=true Performance Considerations

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © DennisBottjer | Powered by: GeeksWithBlogs.net