Signing a .pdb file
I would like to distribute my .pdb files through a ClickOnce install, but I cannot do it because the system does not want to sign the ClickOnce manifest when the .pdb are unsigned. And without a signed manifest, no ClickOnce.
How do you sign them.
I might be able do it by calling sn.exe in the build events, but is there an easier way built into Visual Studio?
How do you sign them.
I might be able do it by calling sn.exe in the build events, but is there an easier way built into Visual Studio?
I very well know what pdb files are.
The idea of distributing them in release is to be able to retrieve more precise information from the stacktrace, such as source code line numbers, when exceptions arise on a test deployment to a few users before committing to a few hundred.
The problem is that Click Once deployment requires that the .pdb be digitally signed, but the compiler does not sign them. I was wondering if there was an easy way to do it because we frequently republish the application during those tests.
The idea of distributing them in release is to be able to retrieve more precise information from the stacktrace, such as source code line numbers, when exceptions arise on a test deployment to a few users before committing to a few hundred.
The problem is that Click Once deployment requires that the .pdb be digitally signed, but the compiler does not sign them. I was wondering if there was an easy way to do it because we frequently republish the application during those tests.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Nobody came with a solution, so I had to find one somewhere else.
Note that when you compile on release mode, pdb files are´nt generated.
You can distribute the Pdb files to other programmers, but I do´nt see advantages for distribution to users on release mode.
Pdb contains information aditional not cotained on assembly like parameter and local variable names on methods.