How to: Update Deployed Office Solutions
When you update an Office solution, use the Publish Wizard to republish the solution to the publish location. The Publish Wizard automatically updates the entire solution with a new version.
Installed solutions automatically check for updates and install them, unless you set the update interval to Never. For more information, see Publishing Office Solutions by Using ClickOnce.
Applies to: The information in this topic applies to document-level projects and application-level projects for Microsoft Office 2010 and the 2007 Microsoft Office system. For more information, see Features Available by Office Application and Project Type.
To update a deployed solution
Ensure that the solution is set up to provide the correct evidence for the security checks.
If the old solution is signed with a trusted certificate, sign the updated solution with the same certificate. If the certificate has expired or cannot be reused, use a certificate that is trusted at the enterprise level.
If the ClickOnce trust prompt was used for trust but the zone has been disabled, the solution will be disabled.
If the signing key was changed, trust must be re-established by using the ClickOnce trust prompt, or the certificate must be trusted at the enterprise level. If the trust is pre-established, the first version will be uninstalled and the updated version will be installed.
If the new certificate is trusted at the enterprise level, then the update takes place with no prompting.
If the new certificate is not trusted, a trust prompt is displayed to the user, if the prompt is allowed.
Use the Publish Wizard to publish the updated Office solution to the same directory as the previous version. For more information, see How to: Publish an Office Solution by Using ClickOnce.
The Office solution is published to a folder at the same directory level as the old solution, but with an incremented version number. The application and deployment manifests are replaced, so the user is automatically directed to the new version the next time the solution checks for updates.
Copy the solution files to the installation location, if it is different from the publish location. Keep the folders and files in the same relative positions.