title: Signing ClickOnce with a certificate?
body: <p>What is the process of obtaining a certificate to sign my <a href="http://en.wikipedia.org/wiki/ClickOnce" rel="noreferrer">ClickOnce</a> assembly(ies)?</p>
  
  <p>I've got a few ClickOnce applications at my company, but they are all signed with temporary certificates created by Visual Studio. Those are obviously not <a href="http://en.wikipedia.org/wiki/Root_certificate" rel="noreferrer">Trusted Root Authorities</a> nor Trusted Publishers. I've followed along the article <em><a href="http://msdn.microsoft.com/en-us/library/ms996418.aspx" rel="noreferrer">Configuring ClickOnce Trusted Publishers</a></em>, and I like the experience when something is signed with a certificate that is both a Trusted Root Authority and Trusted Publisher (that is, no prompt, just an install).</p>
  
  <ol>
  <li>Can I use the same certificate to sign multiple ClickOnce assemblies?</li>
  <li>How much does a certificate cost?</li>
  <li>What information do I need to provide when obtaining the certificate?</li>
  <li>Does the certificate need to be aware of where the publishing location is? For example, if I currently have my ClickOnce applications available from <code>http://apps.mycompany.com/</code> and I want to change this later, for example <code>http://www.mycompany.com/apps</code> or <code>http://apps.mysubcompany.com</code>, will I have to obtain another certificate?</li>
  <li>Are there recommended publishers to obtain from for ClickOnce signing (for example, someone who might already be in an Windows&nbsp;XP, Windows&nbsp;Vista, or Windows&nbsp;7 Trusted Root Authority store)?</li>
  <li>How can I streamline installation to the Trusted Publisher store?</li>
  </ol>