BurnOutSharp 2.6.0

This is a major update to the 2.5.* releases:

• Relicensing to MIT license from GPL 3.0
• Add and update models to better reflect actual structures
• Add native support for MS-CAB (all compressions) based on LibMSPackSharp
• Add native support for Valve archives based on HLLibSharp
• Enable printing for more file types
• Add extraction for a subset of file types to Test
• More library separation
• Add build targets for Windows x86, Windows x64, Linux x64, and OSX x64
• The normal gambit of added, updated, and fixed protections

BurnOutSharp 2.5.0

This is a major update to the 2.3.* releases:

• Proper .NET 6.0 support added (some external dependencies are not supported)
• psxt001z has been split into its own library
• File type determination has been converted into a set of methods
• Radically new library structure created
  • Separate libraries for matching, executable models, builders, and wrappers
  • Replaces poorly-implemented executable code
  • Matching includes Stream implementations
  • All executable checks use new framework
  • Many checks have changed how and what they search for as a result
• Numerous new protections and checks have been added (TheRogueArchivist)
• Many investigative notes have been added (TheRogueArchivist)
• Test executable gained the ability to print executable information

BurnOutSharp 2.3.4

This is a minor update to 2.3.3:

• Fix csproj to include all required libraries by default AND fix nuspec generation

BurnOutSharp 2.3.3

This is a minor update to 2.3.2:

• Fix the nuspec generation that included submodules as Nuget dependencies

BurnOutSharp 2.3.2

This is a minor update to 2.3.1:

• Improved Alpha-ROM detection
• Minor updates for SafeDisc
• CDS-adjacent changes
• Rewrite CD-Lock detection
• Fix a small latent bug in a helper
• Add the exception to full output if something happens

BurnOutSharp 2.3.1

This is a minor update to 2.3.0:

• Fix the nuspec generation that included submodules as Nuget dependencies

BurnOutSharp 2.3.0

This is a major update to the 2.0.* releases:

• Scanner use and internals changed, including flags
• Major overhauls to library usage
• Major additions and updates from @TheRogueArchivist
• Reorganization of namespaces
• New code support for entry point and overlay

BurnOutSharp 2.1.0

This is a minor update to the 2.0.* releases:

• Add AutoPlay Media Studio installer detection and update Setup Factory
• Move more things to PortableExecutable for better performance and stability
• Fix over-matching SafeLock check
• Upgrade to VS2022 solution and AppVeyor
• Convert library to .NET Standard 2.0
• Add .NET 6.0 as build target for test executable
• Update UnshieldSharp and WiseUnpacker to newest versions

BurnOutSharp 2.0.0

This is a major overhaul and a breaking change compared to the 1.x releases:

• Removal of known over-matching checks
• Locking of full file scans behind the debug flag
• Move to stream-based internals
• Many new checks and a few new protections and packers
• Increased accuracy and speed

For those using the test executable, you may notice some changes:

• New flags have been added to allow for more granular scanning of input files and folders
• Drag and drop functionality still works, but debug is not enabled by default anymore

BurnOutSharp 1.8.0

This is a major overhaul and breaking change compared to the 1.7.x releases:

• IncludePosition flag has been renamed to IncludeDebug for future expandability
• Added a few new protection and packer checks
• Removed EVORE helper class (which attempted to run some executables in very specific circumstances)
• Updated, fixed, and implemented PE and NE executable reading (only a few gaps missing)
• Converted the vast majority of content checks to use the new PE and NE reads instead
• Reduced the surface area of the majority of content checks - reduced possible false positives
• Validated as many checks as possible locally instead of relying purely on community feedback

For those using the test executable, you may notice some changes:

• Not all protections will show positions (or the position within the file may seem incorrect) when the IncludeDebug flag is set to true. This is because, where possible, checks have been reduced to more concrete locations and executable sections, therefore making the found position mostly obsolete
• If an uncaught exception occurs, more information will be printed out to the textfile. This was an oversight on my part originally.