Benefits of Disable Debug Mode in ASP.NET

What activity happens on the server when we leave debug mode is true?

#1. It disables page timeouts
#2. It disables compiler optimizations to make symbols close to the actual source code statement
#3. To improve compilation time, it disables some of batch optimization
#4. Increase memory footprint of the application
#5. Disables caching of WebResources.axd (browser will download the associated script files again for every page),
#6. Disables compression of WebResources.axd resources
#7. Disables both page and JIT compiler optimizations


To enable or disable debugging, update the debug value in Web.Config accordingly

compilation debug="true/false"


But, if you want to enforce all site(same server) owner then make the below update in Machine.Config

#1. This will enforce the 'debug' flag to false in every web.config on the machine.
#2. It will disable page output tracing and custom error pages to be shown to remote users instead of the real error messages.

* This value can only be set at the machine level, not at the application level.

* This setting overrides some application level security settings used for debugging

<configuration>
            <system.web>
                <deployment retail="true"/>
            </system.web>
</configuration>



Comments

Popular posts from this blog

Difference between Parse/TryParse/ParseExact/TryParseExact

Benefits of Test Driven Development (TDD)

Version history of C#