Before your 2007 Microsoft Office solutions can run, a few components need to be installed on the computer, such as the .NET Framework 3.5 and the Microsoft Visual Studio Tools for the Microsoft Office system (version 3.0 Runtime). You can often deploy these components along with your solution. For a list of required components, see Office Solution Prerequisites for Deployment (2007 System) and How to: Install Prerequisites on End User Computers to Run Office Solutions (2007 System).

In addition, you need to consider how to trust solutions. For information about security, see Security in Office Solutions (2007 System).

When you deploy an Office solution, you can use the Publish Wizard or the Publish property page to configure the following deployment settings:

• Version number.

• Prerequisites.

• Update intervals.

After you configure these deployment settings, Visual Studio Tools for Office publishes the solution files to the publish location.

Deploying from CD

Deploying Document-Level Solutions

After the solution is copied to the installation location, end users can download and install it. You can install solutions in several different ways: by running the Setup program, by opening the deployment manifest (.vsto file), or by opening the document. For more information, see How to: Install a ClickOnce Office Solution (2007 System) and How to: Uninstall a ClickOnce Office Solution (2007 System).

If your users will install the solution by opening the deployment manifest, you might have to configure the IIS server to recognize the .vsto MIME type. For more information, see How to: Prepare IIS for Deployment of Office Solutions (2007 System).

If you want to create a custom Setup program for your Office solution, you can run the Office solution installer (VSTOInstaller.exe) directly. For more information, see Customizing Office Solution Installation (2007 System).

You can configure a solution to check for updates at specified intervals, and install updates automatically. The default setting for automatic updates is every seven days. After this interval is set and the solution is installed, the interval cannot be changed without installing an update. If your users want to force an update outside of the regular update intervals, the Office solution can be updated manually.

You can deploy updates by using the Publish Wizard. The Publish Wizard generates a new application manifest and copies the solution files to the same publish location as the earlier version.

The publish action also updates the deployment manifest to point to the location of the new version of the solution. When the end user's installed solution checks for updates at the specified interval, it will download and install the most recently deployed version. You can update versions of a solution by updating the manifests and solution files at the deployment location. For more information, see How to: Update Deployed Office Solutions (2007 System).

To roll back to a previous version of a Office solution, see How to: Roll Back a ClickOnce Office Solution to an Earlier Version (2007 System).

For situations where the publish location has changed, the path can be changed in the Setup program without going back to Visual Studio to use the Publish Wizard or Publish page of the Project Designer. For more information, see How to: Change the Installation Path of an Office Solution (2007 System).

You can manually edit application and deployment manifests in Visual Studio Tools for Office solutions. Application and deployment manifests must be re-signed after they are edited by using the Manifest Generation and Editing Tool (mage.exe). For more information, see How to: Change Deployment Properties and Re-Sign Manifests (2007 System).

Starting in Visual Studio 2008 Service Pack 1 (SP1), updates are optional and users can cancel any solution update during the download stage and still run the add-in.

If you test your application-level add-in by publishing and installing the solution on your development computer, uninstall the solution before re-publishing or making more code changes and re-testing by pressing F5. When you install a published solution, the assembly for the add-in is installed into the ClickOnce cache. The Setup program also creates registry keys so the Office application can find and load the assembly. Because rebuilding the solution updates the registry keys, it is necessary to uninstall the first version before publishing or running the second version.

When you install a published solution, the assembly for the add-in is installed into the ClickOnce cache. The Setup program also creates registry keys so the Office application can find and load the assembly. Because rebuilding the solution updates the registry keys, it is necessary to uninstall the first version before publishing or running the second version.

In order to test your deployment on your development computer, create another user account to install and test the application-level add-in.

If you develop multiple Visual Studio Tools for Office solutions, all of the Visual Studio Tools for Office add-ins run because a build is considered an installation. We recommend that you run the Clean Solution command on the Build menu before closing a solution.

ClickOnce Office solutions are installed into the ClickOnce application cache. The ClickOnce cache is a family of hidden directories that holds all of the solution's files, including the assemblies, configuration files, application and user settings, and data directories. ClickOnce Office solutions use the same cache as Windows Forms ClickOnce applications. Links to other Internet or network locations can be opened while working from the ClickOnce cache, and the cached solution can also function in an offline mode. For document-level customizations, the document is not installed into the ClickOnce cache, and can be located on a user's computer or a network file share. For more information about the ClickOnce cache, see ClickOnce Cache Overview.

Data Migration When Updating Solutions

Data Files

Concepts

Other Resources