If you have ever performed website optimization then it is likely you have read this article here. This article discusses the impact of having the debug set to true in your production application. In another one of my blogs on C#, I made the comment once about “what is a technical blog without a comparison of String vs. Stringbuilder” so I thought that same here on my IIS blog that “what is a technical blog without a debug=true entry”. Therefore, here goes! Be warned, that this is an article about how to find the value in your configuration and not a discussion about the impact of it.
One important concept to understand is the Configuration Hierarchy and Effective Configuration. In summary, it means that any setting at a lower level override that same setting made at a higher level. So if you set debug=false in the machine.config file for a given .NET version, but the debug value is set to true in a web.config of the website, then for that website, debug=true. Figure 1 shows the configuration hierarchy for IIS 7+.
Figure 1 – IIS 7, IIS 7.5 and IIS 8 configuration hierarchy
There are a number of places where you can set the value of debug. Review this article which describes the compilation element and the location in which it can be set. Here is the link. Figure 2 shows how the setting exists in a websites web.config file.
Figure 2, setting the debug=true in the web.config file
You can also check the value of this setting in the Configuration Editor on the specific website, as shown in Figure 3. Notice the ‘Section’ and ‘From’ values.
Figure 3, Configuration Editor showing the compilation element for viewing the debug value
If you have some memory dumps of this process you can also review them in WinDbg. In WinDbg, a command I always execute when I review a memory dump is !findDebugTrue. Figure 4 shows the output of the command when the value is true.
Figure 4, WinDbg output for !findDebugTrue when value is true
Finally, Figure 5 shows the output from the same command when the value is false.
Figure 5, WinDbg output for !findDebugTrue when value is false
There you have it, the debug=true blog. But really, use this only for your testing environments and change the value when migrating it to production. It does have some performance impact.