If you sign the solution, you can use the certificate as evidence to grant trust to the solution. You can use the same certificate for multiple solutions, and all solutions can be trusted without updating the security policy.

Applicable to: The information in this topic applies to document-level projects and application-level projects in Office 20 13 and Office 20 10. For more information, see Features by Office Application and Project Type.

If you manually edit the application manifest and deployment manifest using the manifest generation and editing tools (mageui.exe and mageui.exe), you must re-sign these manifests before you can use them. For more information, see How to: Re-sign Applications and Deployment Manifests.

Sign with a certificate

A certificate is a file that contains the unique key and identification of the solution publisher. You can buy a certificate from a certificate authority, or you can create your own certificate and sign it by a certificate authority.

To enable debugging, Visual Studio will sign the Office solution with a temporary certificate. You should not use temporary certificates as evidence in a deployed solution.

Sign an Office solution with a certificate

On the Project menu, click Solution Name Properties.

Click the Signature tab.

Select the signature ClickOnce list.

Find the certificate by clicking Select from Store or Select from File and navigating to the certificate.

To verify that the correct certificate is used, click More Details to view the certificate information.