Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

How to: Deploy Customizations Manually

Note Required applications

The features in this topic are available only if you have the required applications installed.

For more information, see Features Available by Product Combination.

  • One of these development environments:

    VSTO 2005

    -or-

    Visual Studio Team System

  • Microsoft Office 2003

If you choose not to use the Publish Wizard, or if the person doing the deployment does not have access to the Publish Wizard, you can copy all of your Microsoft Visual Studio 2005 Tools for the Microsoft Office System solution files to the deployment destination manually. This topic provides information about manually deploying document-level customizations. For information about deploying application-level add-ins, see Deploying Application-Level Add-ins.

There are two main models for manually deploying document-level customizations:

  • You can enable versioning by duplicating the method that the Publish Wizard uses. This method uses deployment manifests and application manifests on a server to identify current versions of the solution, and downloads updated assemblies to each end user automatically. Older versions of the solution can be kept on the server and used as necessary.

  • You can simply copy the document and assembly to their deployment locations without the manifests, and update the document to point to the assembly. To update an assembly, you replace the existing version with the updated one.

Deployment Using Manifests on a Server

Using this method, you must create an application manifest and deployment manifest for the solution manually. If you use the Publish Wizard, the manifest files are created for you. For more information, see How to: Deploy Solution Files Using the Publish Wizard.

To deploy solution files with manifests

  1. Build the release version of your solution.

  2. At the deployment destination, create one directory folder to hold the document and the deployment manifest.

  3. Create another folder inside the document folder to hold the assemblies and the application manifest. Include the version number of the main project assembly in the name of the folder so that you can keep track of code updates, for example \ExcelApplication1_1.0.0.0. Whenever you update the assembly code, you should create a new assembly folder with the new version number.

  4. Create an application manifest for the solution, and place it in the assembly folder at the deployment destination. For more information, see Application Manifests for Office Solutions.

  5. Create a deployment manifest, and place it in the document folder at the deployment destination. For more information, see Deployment Manifests for Office Solutions.

  6. Copy the assemblies from the project's output folder to the assembly folder at the deployment destination.

  7. Update the application manifest that is embedded in the solution document to point to the deployment manifest location. For more information, see How to: Change the Path to the Deployment Manifest Programmatically.

  8. Copy the solution document from the project's output folder to the document folder at the deployment destination.

  9. Grant full trust to the main project assembly, and grant the appropriate level of permissions to all referenced assemblies. Depending on your deployment model, you might also need to grant full trust to the document. For more information, see Deployment Models and Security Requirements to Run Office Solutions.

Deployment without Manifests

To deploy solution files without manifests

  1. Build the release version of your solution.

  2. Modify the application manifest that is embedded in the document so that it points to the final deployment location of the assembly. By default, the application manifest uses a relative path to point to the directory that the document is in. For more information, see How to: Update Application Manifest Assembly Paths Programmatically.

  3. Copy the document and the assembly to their deployment destinations on end user computers or on servers. For more information, see Deployment Models.

  4. Grant full trust to the main project assembly, and grant the appropriate level of permissions to all referenced assemblies. Depending on your deployment model, you might also need to grant full trust to the document. For more information, see Deployment Models and Security Requirements to Run Office Solutions.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft