Skip to content

Latest commit

 

History

History
53 lines (38 loc) · 3.44 KB

File metadata and controls

53 lines (38 loc) · 3.44 KB
title Custom document properties overview
description Learn that when you build a document-level project, Visual Studio adds two custom properties to the document in the project.
ms.date 02/02/2017
ms.topic concept-article
dev_langs
VB
CSharp
helpviewer_keywords
documents [Office development in Visual Studio], custom properties
custom document properties
document-level customizations [Office development in Visual Studio], custom properties
Office documents [Office development in Visual Studio], custom properties
_AssemblyLocation property
_AssemblyName property
author John-Hart
ms.author johnhart
ms.subservice office-development

Custom document properties overview

When you build a document-level project, Visual Studio adds two custom properties to the document in the project: _AssemblyLocation and _AssemblyName. When a user opens a document, the Microsoft Office application checks for these custom document properties. If they exist in the document, the application loads the Visual Studio Tools for Office runtime , which starts the customization. For more information, see Architecture of Office solutions in Visual Studio.

[!INCLUDEappliesto_alldoc]

_AssemblyName

This property contains the CLSID of an interface in the Office solution loader component of the Visual Studio Tools for Office runtime . The CLSID value is 4E3C66D5-58D4-491E-A7D4-64AF99AF6E8B. You should never change this value.

_AssemblyLocation

This property contains a string that provides details about the deployment manifest for the customization. For more information about manifests, see Application and deployment manifests in Office solutions.

The _AssemblyLocation property value can have different formats, depending on how the solution is deployed:

  • If the solution is published to be installed from a Web site, UNC path, or a CD or USB drive, the _AssemblyLocation property has the format DeploymentManifestPath|SolutionID. The following string is an example:

    file://deployserver/MyShare/ExcelWorkbook1.vsto|74744e4b-e4d6-41eb-84f7-ad20346fe2d9

  • If you are running or debugging the solution from Visual Studio, the _AssemblyLocation property has the format DeploymentManifestName|SolutionID|vstolocal. The following string is an example:

    ExcelWorkbook1.vsto|74744e4b-e4d6-41eb-84f7-ad20346fe2d9|vstolocal

    The SolutionID is a GUID that the Visual Studio Tools for Office runtime uses to identify the solution. The SolutionID is automatically generated when you build the project. The vstolocal term indicates to the Visual Studio Tools for Office runtime that the assembly should be loaded from the same folder as the document.

Related content