Export (0) Print
Expand All
1 out of 7 rated this helpful - Rate this topic

How to: Deploy Office Solutions

There are different steps for deploying the two types of projects:

  • Document-level customizations.

  • Application-level add-ins.

Each type of solution can be deployed in several ways, depending on the deployment model you are using.

For more information about the deployment models for Microsoft Visual Studio 2005 Tools for the Microsoft Office System solutions, see Deployment Models. For more information about document-level customizations and application-level add-ins, see Office Solutions Architecture Overview.

Deploying Document-Level Customizations

To deploy your document-level customizations, you must deploy these components:

  • A Microsoft Office Word 2003 or Microsoft Office Excel 2003 file (template, document, or workbook) that the end user works in.

  • An assembly that contains your compiled custom code, plus any referenced assemblies.

Optionally, to take advantage of automatic assembly updates for the end user you must also deploy:

  • An application manifest. If you use the Publish Wizard, this file is created for you.

  • A deployment manifest. If you use the Publish Wizard, this file is created for you.

For more information, see Deploying Document-Level Customizations. For information about prerequisites for running Office solutions on the end user's computer, see How to: Prepare End User Computers to Run Office Solutions.

To deploy the assembly on a network and the document as a local copy

  1. In Visual Studio, use the Publish Wizard to deploy your solution to a server. For more information, see How to: Deploy Solution Files Using the Publish Wizard.

    For information on how to publish to a test server and then move the solution to a production server, see How to: Change the Location of Document-Level Customizations.

  2. Make changes to security policy so that each end user can run the solution. For more information, see Security Requirements to Run Office Solutions.

  3. Distribute copies of the document or workbook to each user.

To deploy local copies of the document and assembly

  1. In Visual Studio, add a Setup project to your solution and configure the options as desired. For more information, see Windows Installer Deployment Tasks.

    The Setup project is used to create a Windows Installer (.msi) file that will install your solution.

  2. If you want to set security policy at the User level, include a custom action in your Setup project that uses the Code Access Security Policy tool (Caspol.exe) to grant permissions to the assemblies for the current user. For more information, see Security Requirements to Run Office Solutions and Code Access Security Policy Tool (Caspol.exe).

  3. Run the custom action at the end of deployment. For more information, see Custom Actions Management in Deployment.

  4. Deploy the Windows Installer file to each end user. If you do not set security policy for the user during installation, you must grant permissions to the assemblies using another method before the solution will run.

NoteNote

For articles that describe how to create and use a Setup project to deploy a document-level customization, see "Deploying Visual Studio 2005 Tools for Office Solutions Using Windows Installer (Part 1 of 2)" (http://go.microsoft.com/fwlink/?linkid=57779) and "Deploying Visual Studio 2005 Tools for Office Solutions Using Windows Installer: Walkthroughs (Part 2 of 2)" (http://go.microsoft.com/fwlink/?linkid=57780).

To deploy the document and assembly on a network

  1. In Visual Studio, use the Publish Wizard to deploy your solution to a server. For more information, see How to: Deploy Solution Files Using the Publish Wizard.

    For information on how to publish to a test server and then move the solution to a production server, see How to: Change the Location of Document-Level Customizations.

  2. Make changes to security policy so that each end user can run the solution. For more information, see Security Requirements to Run Office Solutions.

Deploying Application-Level Add-ins

To deploy your add-in, you must deploy these components:

  • An assembly that contains your compiled add-in code, plus any referenced assemblies.

  • The application manifest for the add-in.

Optionally, to deploy your add-in to a network location to take advantage of automatic assembly updates for the end user, you must also deploy a deployment manifest. If you use the Publish Wizard, this file is created for you.

For more information, see Deploying Document-Level Customizations. For information about prerequisites for running Office solutions on the end user's computer, see How to: Prepare End User Computers to Run Office Solutions.

To deploy the add-in assembly on a network

  1. In Visual Studio, use the Publish Wizard to deploy your solution to a server. For more information, see How to: Deploy Solution Files Using the Publish Wizard.

    For information about how to publish to a test server and then move the solution to a production server, see How to: Change the Location of Application-Level Add-ins.

  2. Make changes to security policy so that each end user can run the solution. For more information, see Security Requirements to Run Office Solutions.

  3. Create the required registry entries on each client computer. For more information, see Deploying Application-Level Add-ins.

  4. Copy the application manifest for the add-in to each client computer. The application manifest must be copied to the location specified by one of the following values under the registry key HKEY_CURRENT_USER\Software\Classes\CLSID\{<add-in CLSID>}\InprocServer32:

    • ManifestLocation (add-ins for Office 2003)

    • Manifest (add-ins for the 2007 release)

    For more information about these registry keys, see Deploying Application-Level Add-ins.

To deploy the add-in assembly on each computer

  1. In Visual Studio, configure the options for the Setup project included in your add-in solution as desired. For more information, see Setup Projects for Application-Level Add-ins.

  2. Grant full trust to the assemblies in each end user's security policy. If you want to set security policy in the Setup project, add a custom action that uses the Code Access Security Policy tool (Caspol.exe) to grant permissions to the assemblies for the current user. For more information, see Security Requirements to Run Office Solutions and Code Access Security Policy Tool (Caspol.exe).

  3. Run the custom action at the end of deployment. For more information, see Custom Actions Management in Deployment.

  4. Deploy the Windows Installer file to each end user. If you do not set security policy for the user during installation, you must grant permissions to the assemblies using another method before the solution will run.

NoteNote

For articles that describe how to modify the default Setup project included with add-in projects, see "Deploying Visual Studio 2005 Tools for Office Solutions Using Windows Installer (Part 1 of 2)" (http://go.microsoft.com/fwlink/?linkid=57779) and "Deploying Visual Studio 2005 Tools for Office Solutions Using Windows Installer: Walkthroughs (Part 2 of 2)" (http://go.microsoft.com/fwlink/?linkid=57780).

See Also

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.