how to keep debug info out of release builds

[Andy B]

How do you tell vs2005 to keep debug info out of your release builds? When I
build a release and a debug version, there seems to be no difference in them
at all...The release builds still have the debug databases with them...

 

[bruce barker (sqlwork.com)]

use deployment projects for the build.

-- bruce (sqlwork.com)

 

[Andy B]

Actually, I figured it out. I have to go into the property pages for each
project, go to the build tabe and select release build. Press the advanced
button and under debug info highlight none and press ok. Now it's better and
cleaned up. Now All I have to do is publish them (one at a time) but its a
start...


"bruce barker (sqlwork.com)"

 

[Brian Williams]

You could also do this:


Visual Studio Configuration Manager: Add two entries, QA and DEV.



Copy Web.Config into four new files, Web.Config.QA, Web.Config.DEV,
Web.Config.release, and Web.Config.debug and make the appropriate changes to
target the desired system.



Add a Build Event Pre-Build event command line:

"$(ProjectDir)CopyConfig.bat" "$(ProjectDir)web.config.$(ConfigurationName)"
"$(ProjectDir)web.config"





Create CopyConfig.bat with the following and add to project root.



@echo off

echo Comparing two files: %1 with %2



if not exist %1 goto File1NotFound

if not exist %2 goto File2NotFound



fc %1 %2

if %ERRORLEVEL%==0 GOTO NoCopy



echo Files are not the same. Copying %1 over %2

copy %1 %2 /y & goto END



:NoCopy

echo Files are the same. Did nothing

goto END



:File1NotFound

echo %1 not found.

goto END



:File2NotFound

copy %1 %2 /y

goto END



:END

echo Done.



Regards,

Brian K. Williams

 

[Mark Rae [MVP]]

Now it's better and cleaned up.

Except that you lose all your stack trace information for exception
notification...

 

[Peter Bromberg [C# MVP]]

if your project configurations specify to build the .pdb files, these are
useful in exception handling for getting the stack trace / line numbers etc.
They don't add any significant overhead in a release build.
--
--Peter
"Inside every large program, there is a small program trying to get out."
http://www.eggheadcafe.com
http://petesbloggerama.blogspot.com
http://www.blogmetafinder.com