title: What is signing ClickOnce manifests for?
body: <p>According to <a href="http://msdn.microsoft.com/en-us/library/zfz60ccf%28v=vs.90%29.aspx" rel="noreferrer">Microsoft</a>, you <em>must</em> sign your ClickOnce application. But it seems to me that it works just fine when I publish it without signing it (by turning off the 'Sign the ClickOnce manifests' option).</p>
  
  <p>I really didn't care and kept the default values (I think I was using a test certificate) until I changed computer and started getting a message telling me that 'The application is signed with a different key than the existing application on the server', which <a href="http://msdn.microsoft.com/en-us/library/ms228673%28v=vs.90%29.aspx" rel="noreferrer">seems</a> will cause my users to stop getting automatic updates. Apparently, VS uses my computer's name to create the key.</p>
  
  <p>So, should I just stop signing my ClickOnce manifests to prevent this kind of error, or is there any benefit from singing it. Also, are these certificates the ones that would cause the 'Publisher: Unknown Publisher' message when installing the application to show my company name instead, or would I need to purchase two different kind of certificates?</p>