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

debug="false" in web.config and <%@ debug="true" ...%> in aspx file => true or false?

P: n/a
Hi,

I put that question already, but it's still not very clear to me, so ...

Assume following option in web.config=
debug="false"

but in one aspx page (test.aspx)
<%@ debug="true" ..%>
Am I right with those statements:
1) 'page test.aspx will be debugged, but all others wil not' ?
2) With other words, the option in aspx file has priority on the same option
in web.config?
3) Omitting the option debug="false" in web.config means debug is on?
4) And finally, omitting option debug="false" in an aspx file has no
consequence?

Thanks
Cas
Aug 28 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
yes the page-level setting will override the application-level setting.
however if you have debug=false in your web.config, then VS won't be able to
debug the application interactively.

i don't know the answer to 3) and 4) below, but i'm sure it is in the docs
if you look it up.
tim
"André" <sv*@sdv.sdwrote in message
news:eL**************@TK2MSFTNGP03.phx.gbl...
Hi,

I put that question already, but it's still not very clear to me, so ...

Assume following option in web.config=
debug="false"

but in one aspx page (test.aspx)
<%@ debug="true" ..%>
Am I right with those statements:
1) 'page test.aspx will be debugged, but all others wil not' ?
2) With other words, the option in aspx file has priority on the same
option in web.config?
3) Omitting the option debug="false" in web.config means debug is on?
4) And finally, omitting option debug="false" in an aspx file has no
consequence?

Thanks
Cas

Aug 28 '06 #2

P: n/a
1) 'page test.aspx will be debugged, but all others wil not' ?

You will only get dbug output for that page, i.e. the compiler will save
the generated code file only for that page, and the pdb only for that
page (I believe). Although if you try to debug in VS2005, VS2005 will
ask you to add a debug=true to web.config
2) With other words, the option in aspx file has priority on the same
option
in web.config?
Sort of
3) Omitting the option debug="false" in web.config means debug is on?
No! Debugging is off by default. You have to turn it on explicitly.
4) And finally, omitting option debug="false" in an aspx file has no
consequence?
Depends (see 1 and 2 above), but by default debugging is off. If you
don't set the debug option on the page then the one in web.config is read,

Kevin Jones

André wrote:
Hi,

I put that question already, but it's still not very clear to me, so ...

Assume following option in web.config=
debug="false"

but in one aspx page (test.aspx)
<%@ debug="true" ..%>
Am I right with those statements:
1) 'page test.aspx will be debugged, but all others wil not' ?
2) With other words, the option in aspx file has priority on the same option
in web.config?
3) Omitting the option debug="false" in web.config means debug is on?
4) And finally, omitting option debug="false" in an aspx file has no
consequence?

Thanks
Cas

Aug 28 '06 #3

P: n/a
Cas
Thanks a lot

"Kevin Jones" <kj**********@develop.comschreef in bericht
news:%2****************@TK2MSFTNGP05.phx.gbl...
1) 'page test.aspx will be debugged, but all others wil not' ?

You will only get dbug output for that page, i.e. the compiler will save
the generated code file only for that page, and the pdb only for that page
(I believe). Although if you try to debug in VS2005, VS2005 will ask you
to add a debug=true to web.config
2) With other words, the option in aspx file has priority on the same
option
in web.config?

Sort of
3) Omitting the option debug="false" in web.config means debug is on?

No! Debugging is off by default. You have to turn it on explicitly.
4) And finally, omitting option debug="false" in an aspx file has no
consequence?

Depends (see 1 and 2 above), but by default debugging is off. If you don't
set the debug option on the page then the one in web.config is read,

Kevin Jones

André wrote:
>Hi,

I put that question already, but it's still not very clear to me, so ...

Assume following option in web.config=
debug="false"

but in one aspx page (test.aspx)
<%@ debug="true" ..%>
Am I right with those statements:
1) 'page test.aspx will be debugged, but all others wil not' ?
2) With other words, the option in aspx file has priority on the same
option in web.config?
3) Omitting the option debug="false" in web.config means debug is on?
4) And finally, omitting option debug="false" in an aspx file has no
consequence?

Thanks
Cas

Aug 28 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.