May 07, 2007 01:25 PM|jminond|LINK
<compilation debug="false"> This is a must for production, unless you need to deploy, like you said you had errors, so you might want to leave as true, untill all errors are sorted.
You may want to look into asp.net 2.0 precompilation options, and web deployment projects for precompiling, and defining deployment rules.
[ http://weblogs.asp.net/scottgu/archive/2005/11/06/429723.aspx ]
<customErrors mode="RemoteOnly"/> -- Decides if you should dsiplay server errrors, or hide them allowing for a custom "polite" error page you design.
Options are RemoteOnly, meaning if you are on the local server, you will get yellow screen messages, if you are a remote client you will get IIS style errors.
<customErrors mode="Off"/> - Always show the real yellow screen errors
Another thing you may want to think about is <Trace enabled="" /> On or Off, Off is more perfomrnace, trace lets you get information.