Search - Articles
DevASP.NET for ASP.NET, VB.NET, XML and C# (C-Sharp) Developers Friday, January 19, 2018

Dev Articles
Search Directory
ASP.NET
VB.Net
C-Sharp
SQL Server
 


Home > Search > Articles & Samples > ASP.NET 2.0 > Tips & Tricks
How do I prevent ASP.NET trace and debug flags from being left enabled inadvertently in a production environment?    Version: 0.00       Price: $0.00   
Total Hits: 15  |  Today: 0 Author: Reuben Frost       Rating:  
Read Reviews | Write Review | Your Rating: 

In the Maching.config file, there is a "deployment" element that you can add and set that will help in this area. Once set, this element will tell the ASP.NET process ignore several security and performance related settings that may have been left enabled inadvertently in the web.config and deployed in a production environment. Adding this element on all of your production servers results in the following:

* The compiler "debug" flag will be set to "false", ignoring all web.config files
* The trace “enabled” flag will be set to "false", ignoring all web.config files
* The customErrors "mode" flag will be set to "On", ignorin..


What's New at DevASP.Net
04/23  A Debug Stopwatch
04/23  The virtual bool bug
04/23  Application.EnableVisualStyles Bu..
04/23  The Process Async Reader Bug
04/23  Load a DBF into a DataTable
04/23  Weird Error: Unable to Validate D..
04/23  ASP.NET and jQuery to the Max
04/23  Fixing Error: "SetConfigurationSe..
04/23  Generics in .NET
04/23  Builder Design Pattern
04/23  Abstract Factory Design Pattern
04/23  Prototype Design Pattern
04/23  Bridge Design Pattern
04/23  Composite Design Pattern
04/23  Decorator Design Pattern
04/23  Validation in .NET Framework 4
04/23  Windows Phone 7: How to Encrypt C..
04/23  Text box to accept only number
04/23  Using the Raw Input API to Proces..
04/23  Study EVM (Earned Value Managemen..

DevASP.Net - Disclaimer - Privacy
© 2002-2010 DevASP.net