1

In VS2010, when I tell a project to be signed with a key file, but DON'T check the "Protect my key file with a password" box (so a .snk file is generated), I can't step into any code in that assembly when debugging. If I provide a password (so a .pfx file is generated), however, I can. I am not delay signing the assembly. Is there any reason I can't step into the code when I don't protect the key file with a password?

Also, I'm using a project reference within the same solution, not a dll reference (so I'm not just missing my symbols file or anything). I have cleaned and rebuilt both solutions many times.

Samuel Meacham
  • 10,215
  • 7
  • 44
  • 50
  • Why would you not add a password to the key file? – Jeremy McGee Oct 20 '11 at 20:24
  • These are all assemblies used internally by a small department with a small development team. Nothing public facing, nothing released into the wild. – Samuel Meacham Oct 20 '11 at 21:49
  • So why sign the files at all? There's no need to do this for internal applications. – Jeremy McGee Oct 21 '11 at 05:35
  • Because I need the assemblies to be installed in the GAC. They are HttpModules that are installed in the root web app in IIS, set up in the root web.config. The only way to do that is to have them in the GAC. – Samuel Meacham Oct 21 '11 at 19:01

0 Answers0