Releases: SerGreen/Appacker
Releases · SerGreen/Appacker
Appacker v1.3.11
Changelog:
- New feature: password protection for packed application. [#19]
Note: it doesn't encrypt files, so don't rely on it to protect something important. - Added an ability to disable progress bar splash screen when launching packed application, even if it takes a long time to unpack it. [#8]
- Added an option to use windowless unpacker tool (as it was before v1.3.4). This makes console window no longer appear for a split-second when launching a packed application. It's recommended for most users. [#16]
There's a downside to using windowless unpacker: you can not read stdout or write to stdin of a packed app [#3], but if you don't need to do that then you should just leave windowless mode checked. If something doesn't work, then try re-packing without windowless unpacker. - Appacker no longer saves settings in the registry. Now it launches with default settings, unless you save last used settings in an
.ini
file. [#14]- There're buttons for creating and deleting settings file in Advanced Options.
- You may choose to save settings in
AppData
directory or in theappacker.ini
file placed next to theappacker.exe
. Local file takes priority if both are present.
Known issue:
- Some application's icons cause an error in a library that i use to extract icons from exe files. I have noticed this only with Aseprite so far and i don't really want to deal with it right now, so i just added a fall back to a default icon in such situation. So please manually assign an icon in such case and report an issue on GitHub if you find more applications that fail to extract an icon.
Appacker v1.3.10
Changelog:
- Microsoft Visual C++ 2005 x86 DLL is now included (hence +1 MB file size)
- Removed warning message when VC 2005 is not installed
- Add support for saving settings in external
appacker.ini
file- You can create this file by clicking a button in Advanced Options
- If this file is present next to Appacker.exe then it will load settings from this file
- It saves advanced options, language and window position and size
- When INI file is present, Appacker will not save language setting in the registry
Appacker.ini
file is optional and is not required to run Appacker.exe
.
Appacker v1.3.9
Changelog:
- Fix not being able to pack when Visual C++ 2005 Redistributable is not installed
- Now it will pack, but FileDescription will not be set (respective setting in advanced options will not be available either)
- Add a warning message when Visual C++ 2005 Redistributable is not installed
- Has a link to download page for it on Microsoft website
Appacker v1.3.8
Changelog:
- Now you can select not only
.exe
files as the main executable, but also.lnk
,.bat
and.cmd
- Option to provide command line arguments to be passed to the main executable with every launch, available in Advanced options
- Option to change
FileDescription
field of the main executable (only.exe
files have it), available in Advanced options- It's used by Windows as a name of a program in "Open with..." dialog, for example
- By default packages no longer have description "Appacker package", it tries to get this parameter from the main exe or leaves it empty
- Icon picture box now supports drag'n'drop to change an icon of the package
- Updated old icons and added some new ones
- Minor fixes and improvements
Appacker v1.3.7
Changelog:
- Fix for packed applications not being able to open files when file path contains white-space characters.
Occured when packed app was launched via command line with arguments or via "Open with..." option in Windows Explorer context menu (issue #9).
Appacker v1.3.6
Changelog:
- Implemented proper support of multi-resolution *.ico icons
- Fixed a crash when using *.ico file that has only 256x256 resolution (issue #5)
Appacker v1.3.5
Changelog:
- Now you can pass arguments to the packed application and they will be further passed to the unpacked target app
Advanced options
button in Appacker:- Self-repackable checkbox is now inside the advanced options
- Option to open the directory with unpacked files in Explorer at launch
- It's possible to change directory to which files will be extracted. You can select:
- Temp directory
- Desktop
- Directory in which packed .exe is located
- Show prompt to select directory manually at every launch
Appacker v1.3.4
Changelog:
- Now unpacker-wrapper redirects target application's I/O when you redirect stdout of the unpacker. That means that you can launch packed app, redirect it's output and receive the output of the target app instead of unpacker-wrapper
KNOWN ISSUE: Now when you launch a packed app, a console window briefly appears and then disappears — this is the console of unpacker.exe. Redirection couldn't be done when unpacker was window-less, so i had to make it console application and hide it as soon as it starts, but it still flashes for a split-second — that's just how Windows works, there's nothing i can do about that. If you don't want this behaviour, i'd suggest you to use Appacker v1.3.3 instead (if don't need I/O redirection functionality that is).
Appacker v1.3.3
Changelog:
- Cosmetic fix for the command prompt interface (now it prints a line like
C:\>
after exit) --dst
flag is now optional. If you skip it, the package will be named after the main exe and it will be saved next to the source app directory- Minor stability improvements
Appacker v1.3.2
Changelog:
- Updated --help message in command line using better argument descriptions from #1