One of the common mistakes we do is setting debug=’true’ in the deployment server.
It leads to many complications such as,
1) The compilation of ASP.NET pages takes longer (since some batch optimizations are disabled)
2) Code can execute slower (since some additional debug paths are enabled)
3) Much more memory is used within the application at runtime
4) Scripts and images downloaded from the WebResources.axd handler are not cached.
The last point particularly means that all client-javascript libraries and static images that are deployed via WebResources.axd will be continually downloaded by clients on each page view request and not cached locally within the browser. This can slow down the user experience quite a bit for things like Atlas, controls like TreeView/Menu/Validators, and any other third-party control or custom code that deploys client resources.
And also when we set debug=true the exception messages are more typically explanatory which leads to expose more information to the Hackers.
For more detail information click at the below link.
http://blogs.msdn.com/tess/archive/2006/04/13/575364.aspx
*Please dont forget to leave a comment before leaving.
No comments:
Post a Comment