mirror of
https://github.com/SabreTools/SabreTools.Serialization.git
synced 2026-02-04 05:36:12 +00:00
[PR #27] [MERGED] Add extraction for installshield executables. #50
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/SabreTools/SabreTools.Serialization/pull/27
Author: @HeroponRikiBestest
Created: 10/23/2025
Status: ✅ Merged
Merged: 10/23/2025
Merged by: @mnadareski
Base:
main← Head:installshield-exe📝 Commits (10+)
e2242fbAdd extractor for installshield executables.616d2ddAdd commenta8c36f0Fix intendation.afc0b30Ensure PRs recursively pull0c20542Rebase6caf368Fix formatting for parsex796c3d0newline before obj.namef89e92cChanged while loop check to a position vs length checke64ad48Specify type for chunkSize19d87acdeclare chunksize as a const int outside of the loop📊 Changes
4 files changed (+176 additions, -2 deletions)
View changed files
📝
.github/workflows/check_pr.yml(+2 -0)➕
SabreTools.Serialization/Models/InstallShieldExecutable/ExtractableFile.cs(+25 -0)➕
SabreTools.Serialization/Readers/InstallShieldExecutableFile.cs(+66 -0)📝
SabreTools.Serialization/Wrappers/PortableExecutable.Extraction.cs(+83 -2)📄 Description
Handles extraction for installshield executables. I know from experience that this probably won't work with earlier installshield executables that have MSIs inside, and potentially some other kind, but those also might be a different format anyways. Either way, the format is pretty simple and the only potential issues I'm worried about is whether something succeeds in getting the start of its overlay parsed like an installshield exe file entry.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.