Dela via


How to: Install a ClickOnce Office Solution (2007 System)

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

  • 2007 Microsoft Office system

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

End users can install document-level customizations and application-level add-ins the following ways:

  • Running the Setup program that is created when you publish your solution. For information about the Setup program, see Publishing Office Solutions (2007 System).

  • Opening the deployment manifest file, which ends with the extension .vsto.

  • Opening a customized document or workbook, if the prerequisites are already installed and the security policy is set up to grant trust to the solution.

To install by using the Setup program

  1. Double-click setup.exe to start the installation.

    The Setup program checks for prerequisites and installs them as necessary if the user account has administrative privileges. For more information, see Office Solution Prerequisites for Deployment (2007 System).

    Next, the Visual Studio Tools for Office runtime checks for correct permissions and evidence, such as a certificate or an entry in the inclusion list.

    Depending on the certificate and level of permissions, a ClickOnce trust prompt might appear. The trust prompt asks the end user to decide whether the solution's publisher is trustworthy, and whether to allow installation or cancel it.

  2. Run the customization or add-in in the application:

    • For document-level customizations, you can open the document that contains the customization directly from the installation location, or you can copy the document to your local computer and then open the file. If the document remains on a network file share, the network location must be added to the trusted locations of the Trust Center in the Microsoft Office application. For more information, see Granting Trust to Documents (2007 System).

    • For application-level add-ins, open the application.

To install by opening a deployment manifest .vsto file

  1. Open the deployment manifest .vsto file to start the installation.

    Note

    This method requires that the Visual Studio Tools for Office runtime be already installed. Also, this installation method does not check for prerequisites. For more information, see Office Solution Prerequisites for Deployment (2007 System).

    Next, the Visual Studio Tools for Office runtime checks for correct permissions and evidence, such as a certificate or an entry in the inclusion list.

    Depending on the certificate and level of permissions, a ClickOnce trust prompt might appear. The trust prompt asks the end user to decide whether the solution's publisher is trustworthy, and whether to allow installation or cancel it.

  2. Run the customization or add-in in the application:

    • For document-level customizations, you can open the document that contains the customization directly from the installation location, or you can copy the document to your local computer and then open the file. If the document remains on a network file share, the network location must be added to the trusted locations of the Trust Center in the Microsoft Office application. For more information, see Granting Trust to Documents (2007 System).

    • For application-level add-ins, open the application.

To install a document-level customization by using Microsoft Office

  • Open the document to start the installation.

    Note

    This method requires that the Visual Studio Tools for Office runtime and .NET Framework 3.5 be already installed. Also, this installation method does not check for prerequisites. For more information, see Office Solution Prerequisites for Deployment (2007 System).

    The Setup program checks for correct permissions in the Trust Center of the Microsoft Office application, and correct evidence, such as a certificate or an entry in the inclusion list.

    Depending on the certificate and level of permissions, a ClickOnce trust prompt might appear. The trust prompt asks the end user to decide whether the solution's publisher is trustworthy, and whether to allow installation or cancel it.

See Also

Tasks

How to: Install Prerequisites on End User Computers to Run Office Solutions (2007 System)

Concepts

Security in Office Solutions (2007 System)

Office Solution Prerequisites for Deployment (2007 System)

Deploying Office Solutions (2007 System)