How to: Change the Installation Path of an Office Solution (2007 System)
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer

How to: Change the Installation Path of an Office Solution (2007 System)

Updated: August 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

  • 2007 Microsoft Office system

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

The Publish Wizard and the Publish page of the Project Designer create a ClickOnce Setup program for your solution. During the publishing process, you can specify the final deployment location for the Setup program, where end users will go to install the solution. This location is called the installation path in the wizard and the Installation Folder URL on the Publish page. This path makes it possible for the application manifest to check for updates. For more information about publishing, see Publishing Office Solutions (2007 System).

You can add or change the installation path after you publish a solution. There are several reasons you might want to change the installation path:

  • The installation path was not known when the Setup program was compiled.

  • The solution files have been copied to a different location.

  • The server that has the installation files has a new name or location.

In these cases, anyone who has administrator permissions on the network can change the installation path of an Office solution.

Update the Setup program in both application-level and document-level solutions.

For document-level solutions, you must also update the path in the document properties.

To change the installation path in the Setup program

  1. Open the Command Prompt window.

  2. Navigate to the directory that contains the previously created Setup program. For more information about this step, see How to: Deploy an Office Solution by Using ClickOnce (2007 System).

  3. Run the Setup program and include the /url parameter, which takes the new installation path as a string. There will be a message that states that the signature of the executable will be invalidated. This means that the certificate used to sign the solution will no longer be valid, and the publisher will be unknown. End users will be shown an extra prompt that asks whether they want to install the solution.

    setup.exe /url="Installation path"

    For example:

    setup.exe /url=""

    To view the current value of the URL, run setup.exe /url.

For documents and workbooks, open the document you want to deploy so you can update the _AssemblyLocation property.

Updating Document-Level Solutions with the New Path

You can update the _AssemblyLocation property from inside the Office application. However, if you created a Ribbon with the startFromScratch property set to true, you might not have access to the properties while the customization is running.

To update the path in the document properties

  1. Click the Microsoft Office Button, point to Prepare, and then click Properties.

  2. Click Document Properties, and then click Advanced Properties.

  3. On the Custom tab, in the Properties list, select _AssemblyLocation.

  4. In the Value box, there is a deployment manifest identifier already present. At the beginning of the identifier, type the fully qualified path of the document followed by a bar, in the format path|identifier.

    As an example, the path could look like this:


    For more information about how to format this identifier, see Custom Document Properties Overview.

  5. Click OK, and then save and close the document.

  6. Run the Setup program without the /url parameter to install the solution in the specified location.




August 2008

Added information about the Ribbon.

Customer feedback.

© 2016 Microsoft