Ship Program Debug Symbols (PDB) files with Releases

Jul 14, 2014 at 4:22 PM
Hi All,

Would it be possible to modify the project to ship the Program Debug Symbols on release? Doing so would make it easier to debug issues without having to perform a local build of the project, and would give line numbers to more quickly locate the source of an issue.

Jul 14, 2014 at 6:18 PM
I'm not sure I understand - you mean your own add-in?

What prevents you from shipping the .PDB files as well?

Jul 14, 2014 at 6:24 PM
Sorry for the ExcelDna Project itself (specifically ExcelDnaPack.exe).
Jul 14, 2014 at 6:30 PM
You mean with the NuGet package?

Jul 14, 2014 at 6:40 PM
Yes as well as the .zip package presented on this CodePlex site if its not too much of a hassle.
Jul 14, 2014 at 6:59 PM
I'm not sure that makes sense.
Can't you just rebuild (the full source is in the .zip) and use the debug version and .pdbs?

I'd certainly not expect them in the regular NuGet packages. But I think NuGet has some way of publishing symbol packages, though I've not tried anything like that.
I'm not sure it's worth it, though ...

Jul 14, 2014 at 7:10 PM
Yup we can rebuild (which is what we did to debug the error).

It is your call, we've found it helpful in the past to squirrel off the symbols in case we need to debug the released binary but perhaps it is overkill as you mention.
Jul 14, 2014 at 8:25 PM
I'll keep it mind and have made a note about it - thanks.
I guess the right approach is a Symbols package on NuGet.