Deploy PDB files into production to ease exception report investigation.

For a long time I believed that PDB as a part of debugging information should not be included in production deployment. Recently my colleague suggested to copy them to simplify exception investigations.

The following SO discussion convinced us that it is a good idea ( at least for web sites).

http://stackoverflow.com/questions/933883/are-there-any-security-issues-leaving-the-pdb-debug-files-on-the-live-servers

These files will not be exposed to the public if kept in the right places (website\bin).

So we decided to deploy the PDBs into production.

BTW, if you include PDBs with your deployments, you don't need to store them in a symbol server,

However we found that PDBs were generated not for all DLLs. After some analysis we believe that MS changed default settings starting from VS 2008 (or may be since VS 2005) and make generation of PDB-only even for release mode. This is why older projects had generation of PDBs disabled.

To change setting in Visual Studio there is an option in the "Project Properties", "Build", "Advanced...".

Change "Debug Info:" to PDB-only.

The screenshots are available in the posthttp://callicode.com/Homeltpagegt/tabid/38/EntryId/24/How-to-disable-pdb-generation-in-Visual-Studio-2008.aspx