title: Clickonce signed application fails with "has a different computed hash than specified in manifest". Mage fails to resolve issue
body: <p>I've been really struggling with this one for days.  I've seen other posts like <a href="https://stackoverflow.com/questions/6231063/clickonce-deployment-error-different-computed-hash-than-specified-in-manifest">ClickOnce Deployment Error: different computed hash than specified in manifest</a>, but the solutions do not seem to work for me.</p>
  
  <p>I have a valid code signing certificate, and have been using it to sign my ClickOnce application for months.  I realized I wasn't signing the executable and dlls themselves, so I attempt to do so.  Now every time I publish and run the setup.exe, it fails with:  "File, xxxxxx.dll, has a different computed hash than specified in manifest."</p>
  
  <p>If I do not sign the exe and Dlls, I can redeploy.  I made sure all copies of the exe/dlls are signed in all directories (Target, Obj) before publishing.  I've tried using Mage/MageUI but have had no success.  Is it possible to configure a ClickOnce install without signed code, then publish signed code?  Seems logical, but perhaps I am missing something.</p>
  
  <p>Thanks,
  Gregg</p>