Update BOS model namespaces

LinearExecutable/Constants.cs

@@ -1,4 +1,4 @@
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     public static class Constants
     {

LinearExecutable/DebugInformation.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The debug information is defined by the debugger and is not controlled by

LinearExecutable/EntryTableBundle.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The entry table contains object and offset information that is used to resolve

LinearExecutable/EntryTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <see href="https://faydoc.tripod.com/formats/exe-LE.htm"/>
     /// <see href="http://www.edm2.com/index.php/LX_-_Linear_eXecutable_Module_Format_Description"/>

LinearExecutable/Enums.cs

@@ -1,6 +1,6 @@
 using System;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     [Flags]
     public enum BundleType : byte

LinearExecutable/Executable.cs

@@ -1,4 +1,4 @@
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The `LINEAR` executable-file header contains information that the loader requires for

LinearExecutable/FixupPageTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The Fixup Page Table provides a simple mapping of a logical page number

LinearExecutable/FixupRecordTableEntry.cs

@@ -1,4 +1,4 @@
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The Fixup Record Table contains entries for all fixups in the linear EXE module.

LinearExecutable/ImportModuleNameTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The import module name table defines the module name strings imported through

LinearExecutable/ImportProcedureNameTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The import procedure name table defines the procedure name strings imported

LinearExecutable/InformationBlock.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The `information block` in the LE header contains the linker version number,

LinearExecutable/ModuleFormatDirectivesTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The Module Format Directives Table is an optional table that allows additional

LinearExecutable/NonResidentNamesTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The resident and non-resident name tables define the ASCII names and ordinal

LinearExecutable/ObjectPageMapEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The Object page table provides information about a logical page in an object.

LinearExecutable/ObjectTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The object table contains information that describes each segment in

LinearExecutable/PerPageChecksumTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The Per-Page Checksum table provides space for a cryptographic checksum for

LinearExecutable/ResidentNamesTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The resident and non-resident name tables define the ASCII names and ordinal

LinearExecutable/ResourceTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The resource table is an array of resource table entries. Each resource table

LinearExecutable/VerifyRecordDirectiveTableEntry.cs

@@ -1,6 +1,6 @@
 using System.Runtime.InteropServices;
 
-namespace BinaryObjectScanner.Models.LinearExecutable
+namespace SabreTools.Models.LinearExecutable
 {
     /// <summary>
     /// The Verify Record Directive Table is an optional table. It maintains a record