<assemblyIdentity> Element (Visual Studio Tools for Office Deployment Reference)

  • Article

Note

Applies to

The information in this topic applies only to the specified Visual Studio Tools for Office projects and versions of Microsoft Office.

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

Project type

  • Document-level projects

  • Application-level projects

Microsoft Office version

  • Microsoft Office 2003

Identifies the deployment of the Visual Studio Tools for Office solution.

When an assemblyIdentity element is a child of the assembly element, it identifies only the version of the deployment manifest.

When an assemblyIdentity element is a child of a dependentAssembly element, it usually identifies an application manifest, in which case only the name and version are relevant. However, if an assemblyIdentity element identifies an assembly, the other attributes must be included.

<assemblyIdentity  
   name
   version
   language
   publicKeyToken
   processorArchitecture
/>

Elements and Attributes

An assemblyIdentity element is required. It contains no child elements and has the following attributes.

Attribute

Description

name

Required. Identifies the friendly name of the deployment for informational purposes.

version

Required. Specifies the version number of the deployment manifest, application manifest, or assembly, in the following format: major.minor.build.revision

language

Identifies the two-part language codes (for example, en-US) of the assembly. This attribute is in the asmv2 namespace. If unspecified, the default is neutral.

publicKeyToken

Specifies a 16-character hexadecimal string that represents the last 8 bytes of the SHA-1 hash value of the public key used to sign the assembly.

processorArchitecture

Specifies the processor. The valid values are msil, x86, IA64, and amd64.

Remarks

The assemblyIdentity element must uniquely identify the deployment manifest, application manifest, or assembly.

Application and deployment manifests in Visual Studio Tools for Office solutions are not signed, as ClickOnce manifests are. The manifests cannot be validated before they are used.

Some of the fields in application and deployment manifests that are generated by the publish tools are not used in Visual Studio Tools for Office solutions, including some fields that identify properties of the assembly such as size and version.

Example

The following code example illustrates an assemblyIdentity element in a Visual Studio Tools for Office deployment manifest. This code example is part of a larger example provided for the Deployment Manifests for Office Solutions (2003 System) topic.

<assemblyIdentity name="ExcelApplication1.application"
    version="1.0.0.1" publicKeyToken="0000000000000000"
    language="neutral" processorArchitecture="msil" 
    xmlns="urn:schemas-microsoft-com:asm.v1" />

See Also

Reference

Deployment Manifests for Office Solutions (2003 System)