One thing I notice on several of my customers is that it really doesn’t matter how waterproof process you have for deploying web applications, and web.config files in particular. You’ll always end up with at least one web app somewhere with Compilation Debug = True. As you all know this hurts performance a lot, compilation takes a lot longer, memory usage increase etc. You can read more about why this is important at Tess blog here.
If you don’t have .NET Framework 2.0 or later installed you should consider using this script I’ve put together to find Compilation Debug within all the web.config files within the specified directory.
Logparser “SELECT logfilename, Text FROM ‘c:\inetpub\wwwroot\*.*’ WHERE Text LIKE ‘%compilation debug%’” –i:TEXTLINE
If you’re on Framework 2.0 or later check out Scott Guthrie’s blog how to make sure this doesn’t happen at all. You also get some other benefits of using this new switch in the Machine.Config Deployment section. http://weblogs.asp.net/scottgu/archive/2006/04/11/442448.aspx