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

Release Builds

P: n/a
In VS.NET 2005, I have C# class library projects and when I switch to conduct
a release build ... the build still creates program debug files (PDB). I
have tried everything.... I have manually deleted all PDBs before conducting
the RELEASE build...

Any known issues with Release builds ?

Any options somewhere I am missing ?

--
Philip
May 11 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Philip wrote:
In VS.NET 2005, I have C# class library projects and when I switch to conduct
a release build ... the build still creates program debug files (PDB). I
have tried everything.... I have manually deleted all PDBs before conducting
the RELEASE build...


If they're inside a Solution you might want to check the
Configuration Manager settings for the solution; it's possibly still
set to build the class library projects as Debug ones.

As far as I can tel the toolbar "Release/Debug" drop down changes
the setting for the solution, not the project.

--
Chris Crowther
Developer
J&M Crowther Ltd.
May 11 '06 #2

P: n/a
kh
philip

to stop pdb files being generated take a look at project properties, build
tab, advanced. Set "Debug Info" to "None".

if you want to keep the default Release configuration unchanged you can
create a new configuration based on the Release configuration and have this
"Debug Info" setting apply only to this new configuration. this can be done
from the Configuration Manager.

Perhaps someone else can clarify why emitting pdb files is the default for
release builds?

kh

May 11 '06 #3

P: n/a
I've found it helpful that Release emits pdb files; it allows me to
step through code without adding the project temporarly to my solution.

What I now do is run my program, goto Debug -> Windows -> Modules. I
find the module I'd like to step into and select Load Symbols and load
the Release pdb. At some point it will ask me to locate source code,
and I tell it where it may find the source for the release module. I
can now step into code.. and this is much simpler to do than temporarly
add the project, retarget references, debug, then undo those changes.

My question is this; why is it a big deal of the pdb gets generated?

May 11 '06 #4

P: n/a
kh
i'm guessing philip's question relates to the output which will be deployed
to user machines, which was why i investigated this "problem" for my own
purposes. deploying debug files does not seem appropriate in this context,
although admittedly it is unlikely to cause problems.

May 12 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.