This article needs additional citations for verification .(October 2025) |
In the .NET Framework, an assembly manifest [1] [2] is a text file containing metadata about the code within a CLI assembly. It describes the relationship and dependencies of the components in the assembly, versioning information, scope information and the security permissions required by the assembly.
The manifest information embedded within an assembly can be viewed using IL Disassembler (ILDASM.exe) which is available as part of Microsoft Windows SDK. [3]
An assembly manifest contains detailed metadata that identifies the files comprising the assembly, references to other assemblies on which it depends, and type reference information that maps exported types to the modules containing their declarations and implementations. This metadata enables the Common Language Runtime to enforce version policies, resolve dependencies, and load the appropriate components at runtime. [4]
The manifest also specifies optional strong names and digital signatures, which provide a unique identity for the assembly and help ensure its integrity and authenticity during deployment and runtime. [5]
The Assembly Manifest Just as metadata describes the types in an assembly, the manifest describes the assembly itself, providing the logical attributes shared by all the modules and all components in the assembly. The manifest contains the assembly name, the version number, the locale, and an optional strong name uniquely identifying the assembly [...]. It also contains the security demands to verify for the assembly [...], as well as the names and hashes of all the files that make up the assembly.