BOS.* -> BOS.*

BinaryObjectScanner.Models/PortableExecutable/ImportTable.cs

@@ -0,0 +1,45 @@
+using System.Collections.Generic;
+
+namespace BinaryObjectScanner.Models.PortableExecutable
+{
+    /// <summary>
+    /// All image files that import symbols, including virtually all executable (EXE) files,
+    /// have an .idata section. A typical file layout for the import information follows:
+    /// 
+    ///     - Directory Table
+    ///       Null Directory Entry
+    ///     - DLL1 Import Lookup Table
+    ///       Null
+    ///     - DLL2 Import Lookup Table
+    ///       Null
+    ///     - DLL3 Import Lookup Table
+    ///       Null
+    ///     - Hint-Name Table
+    /// </summary>
+    /// <see href="https://learn.microsoft.com/en-us/windows/win32/debug/pe-format"/>
+    public sealed class ImportTable
+    {
+        /// <summary>
+        /// The import information begins with the import directory table, which describes the
+        /// remainder of the import information. 
+        /// </summary>
+        public ImportDirectoryTableEntry[] ImportDirectoryTable;
+
+        /// <summary>
+        /// An import lookup table is an array of 32-bit numbers for PE32 or an array of 64-bit
+        /// numbers for PE32+.
+        /// </summary>
+        public Dictionary<int, ImportLookupTableEntry[]> ImportLookupTables;
+
+        /// <summary>
+        /// These addresses are the actual memory addresses of the symbols, although technically
+        /// they are still called "virtual addresses".
+        /// </summary>
+        public Dictionary<int, ImportAddressTableEntry[]> ImportAddressTables;
+
+        /// <summary>
+        /// One hint/name table suffices for the entire import section.
+        /// </summary>
+        public HintNameTableEntry[] HintNameTable;
+    }
+}