How to: Update Deployed Assembly Files (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. |
When you update a Visual Studio Tools for Office project assembly, use the Publish Wizard to copy the assembly to the deployment location. Using the Publish Wizard takes care of versioning the assembly and updating the application and deployment manifests.
To update a deployed assembly
Ensure that the rebuilt assembly has the correct evidence to be trusted by your deployed solutions, such as a strong name or signature.
Use the Publish Wizard to deploy the assembly. For more information, see How to: Deploy Solution Files Using the Publish Wizard (2003 System).
The assembly is deployed to a folder at the same directory level as the old assembly, but with an incremented version number. For more information, see Deploying Document-Level Customizations (2003 System) and Deploying Application-Level Add-Ins (2003 System).
If necessary, make changes to security policy so that each end user can run the solution. For more information, see Security Requirements to Run Office Solutions (2003 System).
The next time an end user uses your solution, the deployment manifest automatically redirects the document or add-in to use the updated assembly. For more information, see Application and Deployment Manifests in Office Solutions.
See Also
Tasks
How to: Update Deployed Office Documents That Use Managed Code Extensions (2003 System)
How to: Change the Location of Document-Level Customizations (2003 System)
How to: Deploy Office Solutions (2003 System)
Concepts
Deployment Models (2003 System)
Deploying Application-Level Add-Ins (2003 System)
Secure Deployment (2003 System)
Deploying Office Solutions (2003 System)