This documentation is archived and is not being maintained.

Deployment Overview (2003 System)

Visual Studio 2008

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

  • Document-level projects

  • Application-level projects

Microsoft Office version

  • Microsoft Office 2003

For more information, see Features Available by Application and Project Type.

To deploy Visual Studio Tools for Office solutions for Microsoft Office 2003 applications, you should understand the deployment options, choose a deployment model, use the available deployment tools, prepare the end user computer, and grant trust to the solution's assemblies.

You can use either a local or a network deployment model with different security requirements for both document-level customizations and application-level add-ins. For more information about the types of deployment, see Deployment Models (2003 System) and How to: Deploy Office Solutions (2003 System).

You can use the Publish Wizard to deploy Visual Studio Tools for Office solutions. For information, see How to: Deploy Solution Files Using the Publish Wizard (2003 System)

For information about how to manually deploy a Visual Studio Tools for Office solution, see How to: Deploy Solution Files Manually (2003 System).

Setup projects can be used to generate a Windows Installer (.msi) file to configure the target computer and install an application-level add-in. For more information, see Setup Projects for Application-Level Add-ins (2003 System).

For Visual Studio Tools for Office, the default version of the Microsoft .NET Framework is version 3.5. However, you can set Microsoft Office 2003 solutions to use version 2.0, 3.0, or 3.5. When you specify a different Framework version, Office 2003 solutions will not prompt the user to install the .NET Framework 3.5. For more information, see How to: Change the Target .NET Framework.