One of the things you want to avoid when deploying an ASP.NET application into production is to accidentally (or deliberately) leave the <compilation debug="true"/> switch on within the application’s web.config file.
Doing so causes a number of non-optimal things to happen including:
-
The compilation of ASP.NET pages takes longer (since some batch optimizations are disabled)
-
Code can execute slower (since some additional debug paths are enabled)
-
Much more memory is used within the application at runtime
-
Scripts and images downloaded from the WebResources.axd handler are not cached
[http://weblogs.asp.net/scottgu/archive/2006/04/11/Don_1920_t-run- production-ASP.NET-Applications-with-debug_3D001D20_true_1D20_- enabled.aspx]