Deploying Office Solutions (2003 System)

Visual Studio Tools for Office solutions for Microsoft Office 2003 applications have a deployment process that differs from the process for the 2007 Office applications. The main considerations involve choosing a local or network deployment model, and setting security correctly for each user.

Deployment Overview

• Deployment Overview (2003 System)
  Provides an overview of how to deploy Visual Studio Tools for Office solutions.

• Deploying Document-Level Customizations (2003 System)
  Discusses what is involved when you deploy a document-level solution, including the deployment directory structure and an introduction to application and deployment manifests.

• Deploying Application-Level Add-Ins (2003 System)
  Discusses what is involved when you deploy an application level solution, including the deployment directory structure and an introduction to application and deployment manifests.

• Setup Projects for Application-Level Add-ins (2003 System)
  Describes the Setup project that is automatically added to your add-in projects.

• Offline Model for Office Solutions (2003 System)
  Discusses issues to consider if your solution requires the assembly to be available during offline use.

• Deployment Models (2003 System)
  Summarizes the main deployment models for Office solutions and discusses their benefits, requirements, and other considerations.

• How to: Deploy Office Solutions (2003 System)
  Provides the steps necessary to deploy your Visual Studio Tools for Office solution, depending on the type of deployment model you choose.

• How to: Deploy Solution Files Using the Publish Wizard (2003 System)
  Explains how to publish a Visual Studio Tools for Office solution to a Web site, network file share, or your local computer.

• How to: Deploy Solution Files Manually (2003 System)
  Provides the basic steps for copying all of your solution files to the deployment destination manually.

• How to: Deploy for Offline Use of Documents (2003 System)
  Describes how to deploy a managed code assembly to a Web server and enable access through an HTTP path.

Preparing End User Computers

• Preparing End User Computers (2003 System)
  Provides an overview of how to prepare end user computers for Visual Studio Tools for Office solutions.

• Secure Deployment (2003 System)
  Discusses security issues related to the deployment of Visual Studio Tools for Office solutions, including issues involving changing security policy and e-mailing documents.

• How to: Prepare End User Computers to Run Office Solutions (2003 System)
  Provides a list of prerequisites that must be installed on a computer before it will run a Visual Studio Tools for Office solution.

Updating Solutions

• Updating Solutions (2003 System)
  Provides an overview of how to update Visual Studio Tools for Office solutions.

• How to: Change the Target .NET Framework
  Explains how to change the version of the .NET Framework that the solution is designed for.

• How to: Change the Location of Document-Level Customizations (2003 System)
  Explains how to redeploy a document-level solution from one server to another and update the manifest files so that they reference the new server.

• How to: Change the Location of Application-Level Add-ins (2003 System)
  Explains how to redeploy an application-level add-in solution from one server to another and update the manifest files so that they reference the location.

• How to: Update Application Manifest Assembly Paths Programmatically (2003 System)
  Explains the code that is necessary to modify an application manifest that is embedded in a Word or Excel solution document so that it points to a new assembly location.

• How to: Change the Path to the Deployment Manifest Programmatically (2003 System)
  Explains the code that is necessary to modify a deployment manifest that is embedded in a Word or Excel solution document so that it points to a new deployment manifest.

• How to: Update Deployed Office Documents That Use Managed Code Extensions (2003 System)
  Demonstrates a way to provide automatic notification to end users that their current Word or Excel solution document is outdated.

• How to: Update Deployed Assembly Files (2003 System)
  Provides the steps necessary to update your assembly file and the manifest files so that the next time your users run the solution, the Office application loads and runs the updated assembly.

Deployment Walkthroughs

• Deployment Walkthroughs (2003 System)
  Provides walkthrough examples of how to deploy Visual Studio Tools for Office solutions.

• Walkthrough: Deploying a Document and an Assembly to a Local Folder (2003 System)
  Demonstrates how to deploy a Word or Excel solution to a new location on the development computer so that the document and the assembly are located in the same folder.

• Walkthrough: Deploying a Document and an Assembly to Different Local Folders (2003 System)
  Demonstrates how to deploy a Word or Excel solution to a new location on the development computer so that the document and the assembly are located in different folders.

• Walkthrough: Deploying a Document to a Local Folder and an Assembly to a Network Folder (2003 System)
  Demonstrates how to deploy a Word or Excel solution so that the document is on the development computer, and the assembly is in a folder on a network computer.

• Walkthrough: Deploying a Document and an Assembly to a Network Folder (2003 System)
  Demonstrates how to deploy a Word or Excel solution so that the document and the assembly are in a folder on a network computer.

• Walkthrough: Deploying a Document-Level Customization Using a Deployment Manifest (2003 System)
  Demonstrates how to publish a Word or Excel solution and then redeploy the solution to a new network location.

• Walkthrough: Deploying a Document-Level Customization Using a Windows Installer File (2003 System)
  Demonstrates how to create a Windows Installer file that can be used to deploy a Word or Excel solution.

Troubleshooting

• Troubleshooting Office Solution Deployment (2003 System)
  Provides information on troubleshooting Visual Studio Tools for Office solutions for Microsoft Office 2003.

Related Sections

• Security in Office Solutions (2003 System)
  Contains topics that explain how Visual Studio Tools for Office solutions incorporate the security features available with the Microsoft .NET Framework.

• How to: Grant Permissions to Documents and Workbooks in Shared Locations (2003 System)
  Discusses how you can use the Office Document Membership Condition to grant permissions only to the documents and workbooks that are in a specific location, rather than to all content, if the location is not secure, or if you are not sure who has permission to upload content.

• Document-Level Samples
  Contains step-by-step walkthroughs that demonstrate ways to use Visual Studio Tools for Office to create code-behind functionality in your Word and Excel solutions.

• Architecture of Visual Studio Tools for Office Solutions
  Explains how managed code Office solutions work from the perspective of the developer and the end user, and includes information about how managed code works with Microsoft Office 2003 documents.

• Application and Deployment Manifests in Office Solutions
  Explains the role of application and deployment manifests in locating assemblies for Office solutions.

See Also

Concepts

Deploying Office Solutions (2007 System)