blocks|key|408191|text|清单维护有关程序集的信息，如版本、名称区域设置和唯一标识程序集的可选强名称。CLR使用此清单信息。清单还包含验证此程序集的安全要求。它还包含组成程序集的所有文件的名称和散列。.NET程序集清单包含程序集中不同模块的加密散列。加载程序集时，CLR将重新计算手头模块的散列，并将其与嵌入的哈希进行比较。如果运行时生成的哈希不同于清单中的哈希，则.NET拒绝加载程序集并引发异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|408192|元数据是指有关数据的数据。元数据生成该程序集中可用的类型，即。类、接口、枚举、结构等，以及它们包含的命名空间、每个类型的名称、其可见性/作用域、它的基类、它实现的接口、其方法和作用域、以及每个方法的参数、类型的属性等等。程序集元数据由高级编译器从源文件自动生成.编译器在多模块程序集的情况下将元数据嵌入目标输出文件、dll、.exe或.netmodule中。|408193|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Manifest maintains the information about the assemblies 
like version, name locale and an optional strong name that 
uniquely identifying the assembly. This manifest 
information is used by the CLR. The manifest also contains 
the security demands to verify this assembly. It also 
contains the names and hashes of all the files that make up 
the assembly. The .NET assembly manifest contains a 
cryptographic hash of different modules in the assembly. 
And when the assembly is loaded, the CLR recalculates the 
hash of the modules at hand, and compares it with the 
embedded hash. If the hash generated at runtime is different 
from that found in the manifest, .NET refuses to load the 
assembly and throws an exception.

Metadata means data about the data. Metadata yields the 
types available in that assembly, viz. classes, interfaces, 
enums, structs, etc., and their containing namespaces, the 
name of each type, its visibility/scope, its base class, 
the interfaces it implemented, its methods and their scope, 
and each method’s parameters, type’s properties, and so on. 
The assembly metadata is generated by the high-level 
compilers automatically from the source files. The compiler 
embeds the metadata in the target output file, a dll, 
an .exe or a .netmodule in the case of multi-module 
assembly.

blocks|key|408222|text|来自“编程.NET组件，第二版”由Juval出版，O‘’Reilly出版第39页第一段：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|408223|元数据：|style|BOLD|408224|元数据是描述.NET程序集中内容的完整方法。深入研究元数据会产生程序集中可用的类型，即。类、接口、枚举、结构等，以及它们包含的命名空间、每个类型的名称、其可见性/作用域、它的基类、它实现的接口、其方法和作用域、以及每个方法的参数、类型的属性等等。程序集元是由高级编译器从源文件自动生成的。编译器在多模块程序集的情况下将元数据嵌入目标输出文件、dll、.exe或.netmodule中。对于包含IL的多模块程序集，任何模块都必须嵌入元数据来描述该模块中的类型。每个针对.NET+CLR的编译器都需要生成元数据并将其嵌入到输出文件中，而且元数据必须是标准格式的。.NET反射广泛地使用元数据信息动态地了解类型信息。
元数据是托管程序集中描述类型、类型名称、方法名称等内容的附加信息(基本上，您可以从反射服务中检索到的信息)。有关更多详细信息，请参阅http://msdn2.microsoft.com/en-us/library/ms404430.aspx。|blockquote|408225|大会宣言：|408226|元数据描述程序集中的内容，而清单则描述程序集本身，提供程序集中所有模块和所有组件共享的逻辑属性。清单包含程序集名称、版本号、区域设置和唯一标识程序集的可选强名称。CLR使用此清单信息。清单还包含验证此程序集的安全要求。它还包含组成程序集的所有文件的名称和散列。.NET程序集清单包含程序集中不同模块的加密散列。加载程序集时，CLR重新计算手头模块的哈希，并将其与嵌入式哈希进行比较。如果运行时生成的哈希不同于清单中的哈希，则.NET拒绝加载程序集并引发异常。这与COM不同，在COM下，可以通过运行恶意代码将原始DLL或EXE文件与具有相同类型库/接口并对系统造成损害的其他文件交换。清单也是由高级编译器从程序集中所有模块的源文件自动生成的。清单只嵌入到一个物理文件中，而且只有一次，因为它对程序集中的所有模块都很常见，而元数据则需要嵌入所有模块。兼容.NET+CLR的编译器必须生成清单，并且应该采用标准格式。使用清单.NET捕获有关其他引用程序集的信息。这确保了版本兼容性，并且程序集可以与它所期望的其他程序集的精确可信集进行交互。清单包含每个引用的程序集名称、公钥(如果有强名称)、版本号和区域设置。在运行此程序集时，.NET保证只使用这些特定程序集，并且只加载兼容版本。
“报表”是一个非常过份的术语。在.NET中，“程序集清单”是程序集中描述版本控制内容的一些元数据。有关更多细节，请参见这里的http://msdn2.microsoft.com/en-us/library/1w45z383.aspx。|408227|您可以阅读有关程序集清单这里的更多信息。|408228|有关整个程序集和模块的元数据称为清单。|408229|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0596007620|1|http://msdn2.microsoft.com/en-us/library/ms404430.aspx|2|http://msdn2.microsoft.com/en-us/library/1w45z383.aspx|3|http://kamleshsingh.wetpaint.com/page/Assembly%2Bmanifest,metadata^0|2|Y|0|0|0|4|0|AC|1I|1|0|0|5|0|GQ|1I|2|0|C|2|3|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|6|7|1A|8|@$A|1B|B|1C|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1D|8|@]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|K|3|L|5|6|7|1H|8|@$A|1I|B|1J|F|G]]|9|@]|C|$]]|$1|M|3|N|5|J|7|1K|8|@]|9|@$A|1L|B|1M|1|1N]]|C|$]]|$1|O|3|P|5|6|7|1O|8|@]|9|@$A|1P|B|1Q|1|1R]]|C|$]]|$1|Q|3|R|5|6|7|1S|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1T|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]|12|$5|V|W|X|C|$Y|13]]|14|$5|V|W|X|C|$Y|15]]]]

From <a href="https://rads.stackoverflow.com/amzn/click/com/0596007620" rel="nofollow noreferrer" rel="nofollow noreferrer">"Programming .NET Components, Second Edition" By Juval Lowy published by O'Reilly</a> Page 39 first paragraph:

Metadata: 

<blockquote>
 Metadata is the complete way of describing what is in a .NET assembly.
 Digging into the metadata yields the types available in that assembly,
 viz. classes, interfaces, enums, structs, etc., and their containing
 namespaces, the name of each type, its visibility/scope, its base
 class, the interfaces it implemented, its methods and their scope, and
 each method’s parameters, type’s properties, and so on. The assembly
 metada is generated by the high-level compilers automatically from the
 source files. The compiler embeds the metadata in the target output
 file, a dll, an .exe or a .netmodule in the case of multi-module
 assembly. In the case of a multimodule assembly ever module that
 contains IL must have the metadata embeded in it to describe the types
 in that module. Every compiler targeted for the .NET CLR is required
 to generate and embed the metadata in the output file, and that
 metadata must be in a standard format. .NET Reflection extensively
 uses the metadata information to know the type information
 dynamically. 
 
 Metadata is additional information in a managed assembly describing things like types, type names, method names, etc (basically, the information that you can retrieve from the Reflection services). See <a href="http://msdn2.microsoft.com/en-us/library/ms404430.aspx" rel="nofollow noreferrer">http://msdn2.microsoft.com/en-us/library/ms404430.aspx</a> for more details.
</blockquote>

Assembly Manifest: 

<blockquote>
 Metadata describes the contents in an assembly, whereas 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, version number, locale and an optional
 strong name that uniquely identifying the assembly. This manifest
 information is used by the CLR. The manifest also contains the
 security demands to verify this assembly. It also contains the names
 and hashes of all the files that make up the assembly. The .NET
 assembly manifest contains a cryptographic hash of different modules
 in the assembly. And when the assembly is loaded, the CLR recalculates
 the hash of the modules at hand, and compares it with the embeded
 hash. If the hash generated at runtime is different from that found in
 the manifest, .NET refuses to load the assembly and throws an
 exception. This is different from COM, under COM it is possible to
 swap an original DLL or EXE file with another, which have same Type
 Libraries/Interfaces and cause damage to the system, by running
 malacious code. The manifest is also generated automatically by the
 high-level compiler from the source files of all modules in the
 assembly. Manifest is embeded to only one physical file and only once
 since it is common for all the modules in an assembly, whereas the
 metadata needs to be embeded all the modules. The .NET CLR compatible
 compilers must generate the manifest and it should be in the standard
 format. Using the manifest .NET captures information about other
 referenced assemblies. This ensures version compatibility, and the
 assembly gets to interact with the exact trusted set of other
 assemblies it expects. The manifest contains every referenced assembly
 name, its public key (if a strong name is available), its version
 number, and locale. While running this assembly, .NET guarantees that
 only these specific assemblies are used, and that only compatible
 versions are loaded.
 
 "Manifest" is a pretty overloaded term. In .NET, an "assembly manifest" is some metadata in an assembly describing versioning stuff. See here <a href="http://msdn2.microsoft.com/en-us/library/1w45z383.aspx" rel="nofollow noreferrer">http://msdn2.microsoft.com/en-us/library/1w45z383.aspx</a> for more details.
</blockquote>

you can read more about assembly manifest <a href="http://kamleshsingh.wetpaint.com/page/Assembly+manifest,metadata" rel="nofollow noreferrer">here</a>

Metadata about the overall assembly and modules is called the manifest

blocks|key|407593|text|元数据描述程序集中的内容，而清单则描述程序集本身，提供程序集中所有模块和所有组件共享的逻辑属性。清单包含程序集名称、版本号、区域设置和唯一标识程序集的可选强名称。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|407594|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Metadata describes the contents in an assembly, whereas 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, version number, locale and an optional strong name that uniquely identifying the assembly.

blocks|key|407601|text|清单:它存储CLR加载程序集所需的程序集的信息(如程序集名称、版本等)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|407602|元数据:它存储程序集的细节，如方法名称、成员等。|407603|这两个文件都是由编译器在将代码转换为MSIL时自动生成的。|407604|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Manifest: it store the information (like name of assemblies, version etc) about the assemblies which is required by CLR to load the assemblies.

Metadata : It store the detail of assemblies like method name, it's members etc. 

Both the files are generated automatically by the compiler when converting the code to MSIL.

blocks|key|353157|text|这是最简单的答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|353158|程序集:包含程序的一个或多个文件。通常是Exe或dll，或者这些文件和其他文件的组合。|353159|Metadata+:包含两个元素:1)程序集元数据2)类型元数据。|353160|1)程序集元数据也称为清单，它包含程序集的名称、版本、区域性、强名称信息、引用的程序集info...etc。|353161|2)类型元数据是程序集的数据类型和方法。|353162|​|353163|📷|atomic|offset|length|353164|353165|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/3f06cc4d6bb8fc47ec4df3808a1bc08b.jpg|imageAlt^0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|16|8|@]|9|@$O|17|P|18|1|19]]|A|$]]|$1|Q|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y|Z|-4]]]]

Here is the simplest answer. 

Assembly : One or more Files comprising your program. Usually Exe or dll or a combination of these and some other set of files

MetaData : Contains both 
1)Assembly Metadata 2) Type Metadata.

1)Assembly Metadata is also known as MANIFEST, It contains Assembly's Name, Versions, Culture, Strong Name Info, Referenced assembly info...etc.

2)Type Metadata is the data types exported and Methods of the assembly.

<a href="https://i.stack.imgur.com/jQp45.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/jQp45.jpg" alt="enter image description here"></a>

I'm learning .NET framework and been reading through Metadata and Manifest. 

<blockquote>
 "Metadata is data about data and Manifest is data about assembly!!"
</blockquote>

Q: So isn't Manifest a metadata?

Then what are its differences?

Difference between Metadata and Manifest

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在学习.NET框架，并一直在阅读元数据和Manifest。“元数据是关于数据的数据，报表是关于汇编的数据！”问:那么声明不是元数据吗？那它有什么区别呢？

问元数据与报表的差异
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问元数据与报表的差异EN