Updating Solutions (2003 System)
Applies to |
|---|
The information in this topic applies only to the specified Visual Studio Tools for Office projects and versions of Microsoft Office. Project type
Microsoft Office version
For more information, see Features Available by Application and Project Type. |
You can update Visual Studio Tools for Office solutions after they have been deployed without having to repeat the full deployment process. There are different processes for document-level customizations and application-level add-ins.
Publishing Updates
Use the Publish Wizard to help automate assembly updates. The wizard automatically increments the version number and updates the application and deployment manifests. For more information, see How to: Update Deployed Assembly Files (2003 System).
Changing the Location of a Solution
You might want to change the location of a published solution, for example by moving it from a testing server to a production server.
For document-level customizations, see How to: Change the Location of Document-Level Customizations (2003 System).
For application-level add-ins, see How to: Change the Location of Application-Level Add-ins (2003 System).
Updating Installation Paths in Manifest Files
You can use the object model of the Visual Studio Tools for Office runtime to programmatically update the application manifest that is embedded in a document to point to a new assembly location. For more information, see How to: Update Application Manifest Assembly Paths Programmatically (2003 System).
To programmatically update the path to a deployment manifest that has been moved, see How to: Change the Path to the Deployment Manifest Programmatically (2003 System).
Notifying the End Users
You can provide automatic notification to end users that the current Office document is outdated and should be replaced with a newer version. For more information, see How to: Update Deployed Office Documents That Use Managed Code Extensions (2003 System).