How to sign the office application
- I created a office 2007 Application using VSTO.Then I moved the whole solution to another system and while building the office application in another system I received the below error message.
Error Message:-
Cannot find the certificate that matches the project system thumbprint. To sign the application and deployment manifests, open the Project Designer, click the Signing page tab, select an existing certificate, and try again.
Please tell me why this message is coming in new system.If I build the same application in older system then the above error message won't come.
Thakur
Answers
Thakur,
When you created the solution on the old system a temporarily certificate was created which is used to sign the VSTO project. Because this certificate is not available on the new system you are required to create a new certificate which is then used to sign the project.
Follow the instruction and the message will disappear.
For more information please see: http://msdn.microsoft.com/en-us/library/bb608607.aspx
Kind regards, Dennis (http://xldennis.wordpress.com/)- Proposed As Answer byTim LiMSFT, ModeratorFriday, November 06, 2009 3:43 AM
- Marked As Answer byTim LiMSFT, ModeratorThursday, November 12, 2009 8:47 AM
- Hello Thakur,
How's this issue going?
Supplement to Dennis' answer, if you need a step by step guide to sign a VSTO solution please follow this link directly:
http://msdn.microsoft.com/en-us/library/bb772096.aspx
Thanks.
Tim Li
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg@microsoft.com
Please remember to mark the replies as answers if they help and unmark them if they provide no help.- Marked As Answer byGopi Krishna Thakur Wednesday, November 11, 2009 12:16 PM
All Replies
Thakur,
When you created the solution on the old system a temporarily certificate was created which is used to sign the VSTO project. Because this certificate is not available on the new system you are required to create a new certificate which is then used to sign the project.
Follow the instruction and the message will disappear.
For more information please see: http://msdn.microsoft.com/en-us/library/bb608607.aspx
Kind regards, Dennis (http://xldennis.wordpress.com/)- Proposed As Answer byTim LiMSFT, ModeratorFriday, November 06, 2009 3:43 AM
- Marked As Answer byTim LiMSFT, ModeratorThursday, November 12, 2009 8:47 AM
- Hello Thakur,
How's this issue going?
Supplement to Dennis' answer, if you need a step by step guide to sign a VSTO solution please follow this link directly:
http://msdn.microsoft.com/en-us/library/bb772096.aspx
Thanks.
Tim Li
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg@microsoft.com
Please remember to mark the replies as answers if they help and unmark them if they provide no help.- Marked As Answer byGopi Krishna Thakur Wednesday, November 11, 2009 12:16 PM
- Thanks.Is there any way to not have this error message after moving the application in new system? Or this message has has to come anyway.
Thakur - Hi Thakur,
If I use a test certificate which created in Signing Page to sign the manifest, when the project is moved to a new system a new certificate will be automatically generated after I select build command in my VS 2008 SP1.
May be you could use a test certificate before your production release.
Thanks.
Tim Li
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg@microsoft.com
Please remember to mark the replies as answers if they help and unmark them if they provide no help. Thakur,
One approach that may work is if You have access to a commercial certificate and install it on both systems so that You can sign projects with it. Unfortunately I'm not able to test it because Windows Vista use a different security solution when creating the pair of keys than when using Windows XP.
Tim - Can You figure out any issues with this approach?
Kind regards,
Dennis
Kind regards, Dennis (http://xldennis.wordpress.com/)


