Issues with distributing PDBs

[legolan]

One if the first first things we do when our customers report errors
that we cannot track down from the message is give them the PDB's to
put in the bin folder so we can get a line number with the error the
next time it happens.

I would rather just ship with the PDBs so we always have that
information. What are the issues with that? Performance? Easier code
decompilation?

Thanks in Advance.

[Victor Hadianto]

With or without the pdb your .NET assemblies will always be easy to
decompile, use obfuscation to protect your source code.
Victor Hadianto
http://www.hadianto.net/destination

[Brian Delahunty]

Why not ship release builds but just use Trace's to keep logs of what's going
on... at least then you could easily find out what method/section of a method
is causing the issue.

You could also then obsfucate your code so it's a lot safer from
decompilation.

Brian Delahunty
Ireland

"legolan" wrote:

One if the first first things we do when our customers report errors
that we cannot track down from the message is give them the PDB's to
put in the bin folder so we can get a line number with the error the
next time it happens.

I would rather just ship with the PDBs so we always have that
information. What are the issues with that? Performance? Easier code
decompilation?

Thanks in Advance.