SabreTools/SabreTools.Models
1
0
Fork 0
mirror of https://github.com/SabreTools/SabreTools.Models.git synced 2026-09-22 14:46:27 +00:00
Code Issues 9 Packages Projects Releases 20 Wiki Activity

Update BOS model namespaces

Browse Source
This commit is contained in:
Matt Nadareski
2023-09-04 00:12:49 -04:00
parent 1055187865
commit 6dc67e3599
373 changed files with 373 additions and 373 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
PortableExecutable/AcceleratorTableEntry.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Describes the data in an individual accelerator table resource. The structure definition

2
PortableExecutable/AssemblyManifest.cs
View File

@@ -1,6 +1,6 @@
using System.Xml.Serialization;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <see href="https://learn.microsoft.com/en-us/windows/win32/sbscs/manifest-file-schema"/>
[XmlRoot(ElementName = "assembly", Namespace = "urn:schemas-microsoft-com:asm.v1")]

2
PortableExecutable/AttributeCertificateTableEntry.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Attribute certificates can be associated with an image by adding an attribute

2
PortableExecutable/BaseRelocationBlock.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The base relocation table contains entries for all base relocations in

2
PortableExecutable/BaseRelocationTypeOffsetFieldEntry.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Type or Offset field entry is a WORD (2 bytes).

2
PortableExecutable/COFFFileHeader.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// At the beginning of an object file, or immediately after the signature

2
PortableExecutable/COFFLineNumber.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// COFF line numbers are no longer produced and, in the future, will

2
PortableExecutable/COFFRelocation.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Object files contain COFF relocations, which specify how the section data

2
PortableExecutable/COFFStringTable.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Immediately following the COFF symbol table is the COFF string table. The

2
PortableExecutable/COFFSymbolTableEntry.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The symbol table in this section is inherited from the traditional

2
PortableExecutable/Constants.cs
View File

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

2
PortableExecutable/CursorAndIconResource.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The system handles each icon and cursor as a single file. However, these are stored in

2
PortableExecutable/DataDirectory.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Each data directory gives the address and size of a table or string that Windows uses.

2
PortableExecutable/DebugDirectoryEntry.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Image files contain an optional debug directory that indicates what form

2
PortableExecutable/DebugTable.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The .debug section is used in object files to contain compiler-generated debug

2
PortableExecutable/DelayLoadDirectoryTable.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The delay-load directory table is the counterpart to the import directory

2
PortableExecutable/DialogBoxResource.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// A dialog box is also one resource entry in the resource file. It consists of one

2
PortableExecutable/DialogItemTemplate.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Defines the dimensions and style of a control in a dialog box. One or more of these

2
PortableExecutable/DialogItemTemplateExtended.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// A block of text used by an extended dialog box template to describe the extended dialog box.

2
PortableExecutable/DialogTemplate.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Defines the dimensions and style of a dialog box. This structure, always the first

2
PortableExecutable/DialogTemplateExtended.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// An extended dialog box template begins with a DLGTEMPLATEEX header that describes

2
PortableExecutable/DirEntry.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains the information necessary for an application to access a specific font. The structure

2
PortableExecutable/Enums.cs
View File

@@ -1,6 +1,6 @@
using System;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
[Flags]
public enum AcceleratorTableFlags : ushort

2
PortableExecutable/Executable.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The following list describes the Microsoft PE executable format, with the

2
PortableExecutable/ExportAddressTableEntry.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The export address table contains the address of exported entry points

2
PortableExecutable/ExportDirectoryTable.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The export symbol information begins with the export directory table,

2
PortableExecutable/ExportNamePointerTable.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The export name pointer table is an array of addresses (RVAs) into the export name table.

2
PortableExecutable/ExportNameTable.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The export name table contains the actual string data that was pointed to by the export

2
PortableExecutable/ExportOrdinalTable.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The export ordinal table is an array of 16-bit unbiased indexes into the export address table.

2
PortableExecutable/ExportTable.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The export data section, named .edata, contains information about symbols that other images

2
PortableExecutable/FixedFileInfo.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains version information for a file. This information is language and

2
PortableExecutable/FontDirEntry.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains information about an individual font in a font resource group. The structure definition

2
PortableExecutable/FontGroupHeader.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains the information necessary for an application to access a specific font. The structure

2
PortableExecutable/HintNameTableEntry.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// One hint/name table suffices for the entire import section.

2
PortableExecutable/ImportAddressTableEntry.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The structure and content of the import address table are identical to those of

2
PortableExecutable/ImportDirectoryTableEntry.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The import information begins with the import directory table, which

2
PortableExecutable/ImportLookupTableEntry.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// An import lookup table is an array of 32-bit numbers for PE32 or an array of

2
PortableExecutable/ImportTable.cs
View File

@@ -1,6 +1,6 @@
using System.Collections.Generic;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// All image files that import symbols, including virtually all executable (EXE) files,

2
PortableExecutable/LoadConfigurationDirectory.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The data directory entry for a pre-reserved SEH load configuration

2
PortableExecutable/MenuHeader.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains version information for the menu resource. The structure definition provided

2
PortableExecutable/MenuHeaderExtended.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Defines the header for an extended menu template. This structure definition is for

2
PortableExecutable/MenuItem.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains information about each item in a menu resource that does not open a menu

2
PortableExecutable/MenuItemExtended.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Defines a menu item in an extended menu template. This structure definition is for

2
PortableExecutable/MenuResource.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// A menu resource consists of a MENUHEADER structure followed by one or more

2
PortableExecutable/MessageResourceBlock.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains information about message strings with identifiers in the range indicated

2
PortableExecutable/MessageResourceData.cs
View File

@@ -1,6 +1,6 @@
using System.Collections.Generic;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains information about formatted text for display as an error message or in a message

2
PortableExecutable/MessageResourceEntry.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains the error message or message box display text for a message table resource.

2
PortableExecutable/NB10ProgramDatabase.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// PDB 2.0 files

2
PortableExecutable/NewHeader.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains the number of icon or cursor components in a resource group. The

2
PortableExecutable/OptionalHeader.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Every image file has an optional header that provides information to the loader.

2
PortableExecutable/RSDSProgramDatabase.cs
View File

@@ -1,7 +1,7 @@
using System;
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// This file describes the format of the pdb (Program Database) files of the "RSDS"

2
PortableExecutable/ResourceDataEntry.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The resource directory string area consists of Unicode strings, which

2
PortableExecutable/ResourceDirectoryEntry.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// A leaf's Type, Name, and Language IDs are determined by the path that is

2
PortableExecutable/ResourceDirectoryString.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// The resource directory string area consists of Unicode strings, which

2
PortableExecutable/ResourceDirectoryTable.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Each directory table is followed by a series of directory entries that

2
PortableExecutable/ResourceHeader.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Contains information about the resource header itself and the data specific to

2
PortableExecutable/SectionHeader.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Each row of the section table is, in effect, a section header. This table

2
PortableExecutable/SecuROMAddD.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Overlay data associated with SecuROM executables

2
PortableExecutable/SecuROMAddDEntry.cs
View File

@@ -1,6 +1,6 @@
using System.Runtime.InteropServices;
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Overlay data associated with SecuROM executables

2
PortableExecutable/StringData.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Represents the organization of data in a file-version resource. It contains a string

2
PortableExecutable/StringFileInfo.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Represents the organization of data in a file-version resource. It contains version

2
PortableExecutable/StringTable.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Represents the organization of data in a file-version resource. It contains language

2
PortableExecutable/TLSDirectory.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <see href="https://learn.microsoft.com/en-us/windows/win32/debug/pe-format"/>
public sealed class TLSDirectory

2
PortableExecutable/VarData.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Represents the organization of data in a file-version resource. It typically contains a

2
PortableExecutable/VarFileInfo.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Represents the organization of data in a file-version resource. It contains version

2
PortableExecutable/VersionInfo.cs
View File

@@ -1,4 +1,4 @@
namespace BinaryObjectScanner.Models.PortableExecutable
namespace SabreTools.Models.PortableExecutable
{
/// <summary>
/// Represents the organization of data in a file-version resource. It is the root