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/ResidentNameTableEntry.cs

@@ -0,0 +1,30 @@
+namespace SabreTools.Data.Models.NewExecutable
+{
+    /// <summary>
+    /// The resident-name table follows the resource table, and contains this
+    /// module's name string and resident exported procedure name strings. The
+    /// first string in this table is this module's name. These name strings
+    /// are case-sensitive and are not null-terminated. The following
+    /// describes the format of the name strings:
+    /// </summary>
+    /// <see href="https://web.archive.org/web/20240422070115/http://bytepointer.com/resources/win16_ne_exe_format_win3.0.htm"/>
+    public sealed class ResidentNameTableEntry
+    {
+        /// <summary>
+        /// Length of the name string that follows. A zero value indicates
+        /// the end of the name table.
+        /// </summary>
+        public byte Length { get; set; } // TODO: Remove in lieu of AnsiBStr
+
+        /// <summary>
+        /// ASCII text of the name string.
+        /// </summary>
+        public byte[] NameString { get; set; } = [];
+
+        /// <summary>
+        /// Ordinal number (index into entry table). This value is ignored
+        /// for the module name.
+        /// </summary>
+        public ushort OrdinalNumber { get; set; }
+    }
+}