Libraries

This change looks dramatic, but it's just separating out the already-split namespaces into separate top-level folders. In theory, every single one could be built into their own Nuget package. `SabreTools.Serialization` still builds the normal Nuget package that is used by all other projects and includes all namespaces.

SabreTools.Data.Models/NewExecutable/ResourceTable.cs

@@ -0,0 +1,34 @@
+using System.Collections.Generic;
+
+namespace SabreTools.Data.Models.NewExecutable
+{
+    /// <summary>
+    /// The resource table follows the segment table and contains entries for
+    /// each resource in the executable file. The resource table consists of
+    /// an alignment shift count, followed by a table of resource records. The
+    /// resource records define the type ID for a set of resources. Each
+    /// resource record contains a table of resource entries of the defined
+    /// type. The resource entry defines the resource ID or name ID for the
+    /// resource. It also defines the location and size of the resource. The
+    /// following describes the contents of each of these structures:
+    /// </summary>
+    /// <see href="https://web.archive.org/web/20240422070115/http://bytepointer.com/resources/win16_ne_exe_format_win3.0.htm"/>
+    public sealed class ResourceTable
+    {
+        /// <summary>
+        /// Alignment shift count for resource data.
+        /// </summary>
+        public ushort AlignmentShiftCount { get; set; }
+
+        /// <summary>
+        /// A table of resource type information blocks follows.
+        /// </summary>
+        public ResourceTypeInformationEntry[] ResourceTypes { get; set; } = [];
+
+        /// <summary>
+        /// Resource type and name strings are stored at the end of the
+        /// resource table.
+        /// </summary>
+        public Dictionary<ushort, ResourceTypeAndNameString?> TypeAndNameStrings { get; set; } = [];
+    }
+}