I have a trusted Silverlight 4 OOB application that was signed with a certificate that expired last week. I could not release the new code in the old certificate.
I applied for a new five-year certificate and re-signed the application after selecting this new certificate from my certificate store (same publisher name, company, etc.).
The Silverlight engine now automatically updates when it tries to upgrade an OOB application to a new version with a certificate mismatch error. This obviously does not like the new certificate.
How can I get around this - I think it depends on the issuer of the certificate to “bind” my certificates in order to continue trusting. I do not want my users to uninstall the software every time my certificate expires and I have to get a new one.
source share