How to: Change the Location of Application-Level Add-ins (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 change the location of a deployed application-level solution, you redeploy it. For example, a developer might publish a solution to a testing server, and the IT department then redeploys the solution to a production server after approval. For Visual Studio Tools for Office solutions to continue to work, the application and deployment manifests must be updated with the new path to the solution files. For more information, see Application and Deployment Manifests in Office Solutions.
There are two types of redeployment scenarios for add-ins:
Editing the application manifest on the client computer.
This scenario is useful in these circumstances:
When the solution files on the server are moved and end users cannot access the files in the old location.
When few end users are using the solution and it is easy to update each user's copy of the application manifest.
Editing the deployment manifest and application manifest on the server.
This scenario is useful in these circumstances:
When the solution files in the old location are still available to all end users.
When many end users are using the solution, and it is difficult to update each user's copy of the application manifest.
Note
Your computer might show different names or locations for some of the Visual Studio user interface elements in the following instructions. The Visual Studio edition that you have and the settings that you use determine these elements. For more information, see Visual Studio Settings.
Editing the Application Manifest on the Client
To redeploy the solution by editing the application manifest on the client
Use the Publish Wizard to publish the solution to the testing server. For more information, see How to: Deploy Solution Files Using the Publish Wizard (2003 System).
The Publish Wizard copies the add-in assemblies to the server, and creates the deployment manifest and a new application manifest.
Copy the assemblies, the deployment manifest, and the new application manifest to the new server location.
There are now two sets of files: one at the old server location and one at the new server location.
Edit the new application manifest so that it points to the new deployment manifest and the new assemblies. For more information, see Application Manifests for Office Solutions (2003 System).
Increase the version of the new application manifest. For more information, see Application Manifests for Office Solutions (2003 System).
Edit the new deployment manifest so that it points to the new application manifest. For more information, see Deployment Manifests for Office Solutions (2003 System).
Increase the version of the new deployment manifest. For more information, see Deployment Manifests for Office Solutions (2003 System).
Update the application manifest that is on the client computer to point to the new deployment manifest location by editing the <installFrom> element that is a child of the <assembly> element. For more information, see Application Manifests for Office Solutions (2003 System).
Note
The application manifest that is installed on the client computer by the Setup project does not have an <installFrom> element under the <assembly> element. If you originally deployed the add-in to the client computer by using the Setup project, you must add the <installFrom> element under the <assembly> element in the application manifest. Alternatively, you can replace the application manifest on the client computer with the application manifest that the Publish Wizard generated.
The next time an end user starts the Microsoft Office application, or the next time an end user disables and re-enables your add-in by using the COM Add-Ins dialog box in the Office application, the add-in will check the new deployment manifest and be redirected to the new application manifest. The add-in will then use the files in the new locations.
Editing the Manifests on the Server
To redeploy the solution by editing the manifests on the server
Use the Publish Wizard to publish the solution to the testing server. For more information, see How to: Deploy Solution Files Using the Publish Wizard (2003 System).
The Publish Wizard copies the add-in assemblies to the server, and creates the deployment manifest and a new application manifest.
Copy the assemblies, the deployment manifest, and the new application manifest to the new location.
There are now two sets of files: one on the old server and one on the new server.
Edit the new application manifest so that it points to the new deployment manifest and the new assemblies. For more information, see Application Manifests for Office Solutions (2003 System).
Increase the version of the new application manifest. For more information, see Application Manifests for Office Solutions (2003 System).
Edit the new deployment manifest so that it points to the new application manifest. For more information, see Deployment Manifests for Office Solutions (2003 System).
Increase the version of the new deployment manifest. For more information, see Deployment Manifests for Office Solutions (2003 System).
Edit the old deployment manifest so that it points to the new application manifest.
Increase the version of the old deployment manifest.
The next time an end user starts the Office application, or the next time an end user disables and re-enables your add-in by using the COM Add-Ins dialog box in the Office application, the add-in will check the old deployment manifest and be redirected to the new application manifest. The add-in will then use the files in the new locations.
See Also
Tasks
How to: Deploy Solution Files Using the Publish Wizard (2003 System)
Concepts
Deploying Office Solutions (2003 System)
Deploying Application-Level Add-Ins (2003 System)