Share via


How to: Change Deployment Properties

You can make changes to deployment properties in an application manifest for application-level add-ins after the manifests have been generated by the Publish Wizard or the Publish tab of the Project Designer. You can make changes to the following properties:

  • The description of an Office solution.

  • The name of an Office solution.

  • The load behavior of an application-level add-in.

After you make these changes, you must re-sign both the application manifest and the deployment manifest with a certificate. Use the Manifest Generation and Editing Tool (Mage.exe) to sign the application and deployment manifests.

Applies to: The information in this topic applies to document-level projects and application-level projects for Microsoft Office 2013 and Microsoft Office 2010. For more information, see Features Available by Office Application and Project Type.

Changing Deployment Properties

You can change the settings of an Office solution by editing the application manifest, and then re-signing both the application and deployment manifest files. For information about the syntax of application manifests, see Application Manifests for Office Solutions.

To change deployment properties

  1. Open the application manifest (.dll.manifest) in a text editor.

  2. Edit the value of the <friendlyname> element to change the add-in name.

    The name of an add-in appears in the list of installed add-ins. For information about the syntax of this element, see <friendlyName> Element (Office Development in Visual Studio).

  3. Edit the <description> element to change the add-in description.

    The description of an add-in appears in the list of installed programs. For information about the syntax of this element, see <description> Element (Office Development in Visual Studio).

  4. Edit the loadBehavior attribute in the <appAddin> element to change the load behavior.

    The load behavior specifies whether an add-in should be loaded at startup, on demand, or on first startup. For information about the syntax of this element, see <appAddin> Element (Office Development in Visual Studio).

  5. Re-sign the application and deployment manifests with the Manifest Generation and Editing Tool (mage.exe). For more information about this procedure, see How to: Re-sign Application and Deployment Manifests.

See Also

Tasks

How to: Publish an Office Solution by Using ClickOnce

How to: Install a ClickOnce Office Solution

How to: Publish a Document-Level Office Solution to a SharePoint Server by Using ClickOnce

Concepts

Creating a Custom Installer for a ClickOnce Office Solution

Other Resources

Deploying Office Solutions

Publishing Office Solutions by Using ClickOnce