1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
//! Owned File structures for the File metadata table.
//!
//! This module provides the [`File`] struct which represents file definitions
//! with resolved references and owned data. Files list the components of
//! multi-file assemblies including modules, resources, and native libraries.
//!
//! # Purpose
//! The File table enables multi-file assembly scenarios:
//! - **Multi-module assemblies**: Additional .netmodule files containing code
//! - **Resource files**: Binary data files (.resources, images, data)
//! - **Native libraries**: Unmanaged DLLs for P/Invoke operations
//! - **Documentation**: Associated help files and XML documentation
//! - **Satellite assemblies**: Localization and culture-specific resources
//!
//! # File Management
//! Files provide assembly composition information:
//! - **Component tracking**: Lists all files that comprise the assembly
//! - **Integrity verification**: Cryptographic hashes ensure file authenticity
//! - **Type classification**: Flags distinguish metadata from resource files
//! - **Reference resolution**: Names enable runtime file location
//!
//! # ECMA-335 Reference
//! See ECMA-335, Partition II, §22.19 for the File table specification.
use crate;
/// Represents a file definition with resolved references and owned data.
///
/// A file entry describes a component of a multi-file assembly, providing metadata
/// about files that are part of the assembly but stored separately from the main
/// manifest. This includes modules, resources, and native libraries.
///
/// # File Types
/// Files can serve various purposes in assemblies:
/// - **Executable modules**: .netmodule files with executable code
/// - **Resource files**: .resources files with binary data
/// - **Native libraries**: .dll files with unmanaged code
/// - **Documentation**: .xml files with API documentation
/// - **Configuration**: Data files with application settings
///
/// # File Attributes
/// The flags field indicates file characteristics:
/// - **`CONTAINS_META_DATA`**: File contains .NET metadata (executable modules)
/// - **`CONTAINS_NO_META_DATA`**: Resource files without metadata
///
/// # Hash Verification
/// Each file includes a cryptographic hash for security:
/// - **SHA-1 or SHA-256**: Algorithm depends on assembly version
/// - **Integrity checking**: Verifies file hasn't been tampered with
/// - **Loading validation**: Runtime can verify file authenticity
/// - **Security assurance**: Prevents malicious file substitution
///
/// # Assembly Integration
/// Files integrate with the broader assembly structure:
/// - **Module loading**: Executable files loaded by the CLR
/// - **Resource access**: Resource files accessed through APIs
/// - **P/Invoke**: Native libraries used for interop
/// - **Documentation**: Help files displayed in IDEs
///
/// # ECMA-335 Reference
/// See ECMA-335, Partition II, §22.19 for the complete File table specification.