By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,558 Members | 1,533 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,558 IT Pros & Developers. It's quick & easy.

Web.config - setting debug="false" - what is lost?

P: n/a
By default, Web.config has the following section:
<compilation
defaultLanguage="c#"
debug="true"
/>

note that debug="true"

There is a comment - also in the default Web.config - that states that
making debug="false" will result in faster performance but a loss of
debugging/.pdb symbols.

My situation and question:
I have a centralized error logger that is called from my app's code-behind
and other custom classes (in the try... catch blocks) that logs important
information about runtime errors. Included in my logs is parts of the stack
trace. Question: If I set debug="false", will I lose that stack trace
information - or any other similar important information? Or does
debug="false" only impact rendered aspx pages?

Thanks!
Nov 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Jeremy S. wrote:
By default, Web.config has the following section:
<compilation
defaultLanguage="c#"
debug="true"
/>

note that debug="true"

There is a comment - also in the default Web.config - that states that
making debug="false" will result in faster performance but a loss of
debugging/.pdb symbols.

My situation and question:
I have a centralized error logger that is called from my app's code-behind
and other custom classes (in the try... catch blocks) that logs important
information about runtime errors. Included in my logs is parts of the stack
trace. Question: If I set debug="false", will I lose that stack trace
information - or any other similar important information? Or does
debug="false" only impact rendered aspx pages?

Thanks!

You will stille get the Exception handling stuff you get right now. You
can NOT attach a debugger and in case of an unhandled exception, you
will not see any sourcecode in that 'yellow screen of death'.

//Rutger
Nov 19 '05 #2

P: n/a
Thanks. Just what I wanted to hear... but you also have my curiosity up -
I've gotten along quite well without using the debugging info that
apparently will not be available (and probably related to the "'yellow
screen of death' to which you refer). Where can I read up on that particular
debugging capability? What is it formally called so I can do a google
search?

Thanks!
"Rutger Smit" <DoDotNet@KICKTHIS_Gmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Jeremy S. wrote:
By default, Web.config has the following section:
<compilation
defaultLanguage="c#"
debug="true"
/>

note that debug="true"

There is a comment - also in the default Web.config - that states that
making debug="false" will result in faster performance but a loss of
debugging/.pdb symbols.

My situation and question:
I have a centralized error logger that is called from my app's
code-behind and other custom classes (in the try... catch blocks) that
logs important information about runtime errors. Included in my logs is
parts of the stack trace. Question: If I set debug="false", will I lose
that stack trace information - or any other similar important
information? Or does debug="false" only impact rendered aspx pages?

Thanks!

You will stille get the Exception handling stuff you get right now. You
can NOT attach a debugger and in case of an unhandled exception, you will
not see any sourcecode in that 'yellow screen of death'.

//Rutger

Nov 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.