Re: How to set for debug/release

Juan,

A further research proved that you're right. What I wrote was correct for
1.1.

K.Scott Allen explains it nicely in
http://odetocode.com/Blogs/scott/archive/2005/11/15.aspx

Always happy to learn,

Eliyahu

"Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message
news:%23M1WQZxVGHA.3736@xxxxxxxxxxxxxxxxxxxxxxx
I'm afraid not, Eliyahu.
Where did you read that it only applies to *.aspx files ?

See : http://msdn2.microsoft.com/en-us/library/2fdbs127.aspx

That page explains that the *Build* configuration option which controls
whether the compilation will generate debugging information is moved
to web.config for VB.NET, C# and J#.

I don't see any exceptions there.

Additionally, that page makes clear that "If a project contains multiple
configurations
(Debug compilation, Release compilation, and so on), conversion follows
this logic:

If the project contains only Debug and Release configurations,
then the Debug configuration is converted to Visual Studio 2005."

That means that, since the default compilation mode is set to <compilation
debug="false">
in the *Master web.config* in the CONFIG directory of the .Net Framework
directory,
all you need to do to generate assemblies with debugging information is
change the
web.config setting to <compilation debug="true">.

If you change that setting for one application (in its web.config), then
only that application
will generate assemblies with debugging information.

If you change it at the master web.config level, all applications will
generate debugging information
( not advisable, as it will impact performace adversely ).





Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Eliyahu Goldin" <removemeegoldin@xxxxxxxxxxxxxx> wrote in message
news:eFpUKzuVGHA.900@xxxxxxxxxxxxxxxxxxxxxxx
Juan,

The setting in web.config affects compiling .aspx files deployed on the
server. It doesn't affect
assembly dlls produced in a development environment and deployed to the
server as binaries.

Eliyahu

"Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message
news:uaPVB0mVGHA.4976@xxxxxxxxxxxxxxxxxxxxxxx
I should have added that, in ASP.NET 2.0, the debug/erelease
choice is set via the web.config file for the application :

<compilation debug = "false">
or
<compilation debug = "true">

The default is "false".




Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message
news:utw$CymVGHA.1236@xxxxxxxxxxxxxxxxxxxxxxx
Eliyahu,

In VS 2003, that choice is available. In VS 2005, it's not.



Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Eliyahu Goldin" <removemeegoldin@xxxxxxxxxxxxxx> wrote in message
news:O9XqqvlVGHA.224@xxxxxxxxxxxxxxxxxxxxxxx
Right-click your solution in the solution explorer and select the
Configuration Manager. You
should also see a dropdown list with word Debug on your standard
toolbar.

Eliyahu

"Joe Befumo" <joe@xxxxxxxxxx> wrote in message
news:442fd2fa$0$5429$b9f67a60@xxxxxxxxxxxxxxxxxxxxx
When I tried debugging for the first time, I pop-up asked me if I
wanted to set the project to
enable debugging. Now I'm ready to release and can't find anyplace to
set the build to
'release'. A pointer would be appreciated. Thanks.

Joe











.