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/InstallShieldExecutable/Constants.cs

@@ -0,0 +1,15 @@
+namespace SabreTools.Data.Models.InstallShieldExecutable
+{
+    public static class Constants
+    {
+        /// <summary>
+        /// The signature for one of two kinds of currently unsupported ISEXE formats.
+        /// </summary>
+        public const string ISSignatureString = "InstallShield";
+
+        /// <summary>
+        /// The signature for one of two kinds of currently unsupported ISEXE formats.
+        /// </summary>
+        public const string ISSetupSignatureString = "ISSetupStream";
+    }
+}

SabreTools.Data.Models/InstallShieldExecutable/FileEntry.cs

@@ -0,0 +1,37 @@
+namespace SabreTools.Data.Models.InstallShieldExecutable
+{
+    /// <summary>
+    /// Set of attributes for each fileEntry in an InstallShield Executable
+    /// </summary>
+    public class FileEntry
+    {
+        /// <summary>
+        /// Name of the file
+        /// </summary>
+        /// <remarks>May only contain ASCII (7-bit) characters</remarks>
+        public string Name { get; set; } = string.Empty;
+
+        /// <summary>
+        /// Path of the file, seems to usually use \ filepaths
+        /// </summary>
+        /// <remarks>May only contain ASCII (7-bit) characters</remarks>
+        public string Path { get; set; } = string.Empty;
+
+        /// <summary>
+        /// Version of the file
+        /// </summary>
+        /// <remarks>May only contain ASCII (7-bit) characters</remarks>
+        public string Version { get; set; } = string.Empty;
+
+        /// <summary>
+        /// Length of the file. Stored in the installshield executable as a string.
+        /// </summary>
+        public ulong Length { get; set; }
+
+        /// <summary>
+        /// Offset of the file.
+        /// </summary>
+        /// <remarks>This is not stored in the installshield executable, but it needs to be stored here for extraction.</remarks>
+        public long Offset { get; set; }
+    }
+}

SabreTools.Data.Models/InstallShieldExecutable/SFX.cs

@@ -0,0 +1,41 @@
+namespace SabreTools.Data.Models.InstallShieldExecutable
+{
+    /// <summary>
+    /// Represents the layout of of the overlay area of an
+    /// InstallShield executable.
+    ///
+    /// The layout of this is derived from the layout in the
+    /// physical file.
+    /// </summary>
+    /// <remarks>
+    /// According to ISx source, there are two categories of installshield executables,
+    /// plain and encrypted. Encrypted has two different "types" it can be, specified by
+    /// a header. "InstallShield" and a newer format from 2015?-onwards called "ISSetupStream".
+    /// Plain executables have no central header, and each file is unencrypted. Files
+    /// in "InstallShield" encrypted executables have encryption applied over block sizes
+    /// of 1024 bytes, and files in "ISSetupStream" encrypted executables are encrypted
+    /// per-file. There's also something about leading data that isn't explained
+    /// (at least not clearly), and these encrypted executables can also additionally have
+    /// their files compressed with inflate.
+    ///
+    /// While not stated in ISx; from experience, executables with "InstallShield" often
+    /// (if not always?) mainly consist of a singular, large MSI installer along with some
+    /// helper files, whereas plain executables often (if not always?) mainly consist of
+    /// regular installshield cabinets within. At the moment, this code only supports and
+    /// documents the plain variant. Clearer naming and separation between the types is yet
+    /// to come.
+    /// </remarks>
+    /// There is no unified header or footer that indicates a file
+    /// table, so having either each file entry cache the data
+    /// or be associated with an offset may make it more useful.
+    ///
+    /// It will need to be made very apparent that the dictionary
+    /// does not directly represent the structure.
+    public class SFX
+    {
+        /// <summary>
+        /// Set of file entries
+        /// </summary>
+        public FileEntry[] Entries { get; set; } = [];
+    }
+}