search

coapp / coapp.powershell

ClrPlus Signing
52 stars 43 forks source link

PDBs are not copied next to DLL in OutputDir of consuming project #46

Open willyd opened 10 years ago

willyd commented 10 years ago

Hi,

I am not sure if this is desired behavior but I think that the PDB file of a DLL should also be copied to the output folder of a consuming project so that the DLL can be debugged.

fearthecowboy commented 10 years ago

Ah right. I'll make sure that gets added

fearthecowboy commented 10 years ago

I have it putting the symbols files into the CopyToOutput item group now, so it should work.

Update to the latest development version (2.4.493.0) to test this--from an elevated powershell prompt:

Update-CoAppTools -development -killpowershells

Thieum commented 9 years ago

I still get the following warning:

warning LNK4099: PDB 'vc110.pdb' was not found with '[package].lib([ClassInPackage].obj)' or at '[PathToProject]\Release\vc110.pdb'; linking object as if no debug info [PathToPackage].lib([ClassInPackage].obj)

Even when using the latest developement version. What could be done to avoid this warning? I hoped copying the pdb would solve it.