Solve the Problem of clickonce signature expiration

Scenario: A project used in the production environment performs system upgrade. When the clickonce release process finds that the signature has expired, the on-site engineer generates a new signature and then releases the product. After the release is completed, all clients cannot be updated and a signature error is prompted.
Problem: the annual signature of vs2005 is only valid for one year, so it is easy to expire during the maintenance period. If the new signature result is made, the client cannot update the verification signature.

Solution:
1. Create a new signature and use the new signature as clickonce.ProgramDelete and re-use the new clickonce installer for installation.
(This method is so shameful. If you have another upgrade, you may have this problem. At the same time, clickonce must be renamed as clickoneyear ).

2. extend the validity period by using the original signature.
Http://support.microsoft.com/kb/925521/zh-cn
Http://support.microsoft.com/kb/925521/en-us

Some of you have found this problem and know the solution. However, if VC ++ is not installed on the machine, it may be inconvenient to perform the operation. Now, you can download the package:
Http://files.cnblogs.com/spymaster/RenewCert.rar
Usage: in the Command window, enter
Renewcert <oldcertificate>. pfx <newcertificate>. pfx \ "cn = <newcertificatename> \" <password>
Okay. The new signature is valid for five years.

3. Make a long-term signature at the beginning of the project.
Http://www.cnblogs.com/xuhaibiao/archive/2009/06/22/1508317.html