PortableApps.com is proud to announce that PortableApps.com Installer 2.0.2 has been released. The PortableApps.com Installer allows you to quickly package your portable apps in an easy-to-use installer without having to write or compile any code. This release fixes issues with plugin/add-on installers. The PortableApps.com Format Specification and installer are now available for outside developers to use and can be used freely with free open source and freeware applications. Commercial use is available by contacting PortableApps.com.
PortableApps.com Installer Features
The PortableApps.com Installer allows you to easily package your portable apps. It features:
- Proven NSIS installer core
- Excellent compression for distribution
- Easy configuration with no coding required
- Multilingual with 70 Languages and Full Unicode Support
- Optional sections
- Automatic integration with the PortableApps.com Platform
- Works from command line and Send To (just pass the portable app's main directory, e.g. X:\PortableApps\FileZillaPortable)
- Interactive mode to assist with missing entries
- Licensed for use with free open source and freeware
- Commercial use by contacting PortableApps.com
What's New in the Format and Installer?
Full Armenian language support has been added. A bug preventing the use of spaces in Optional component names and registry entries has been fixed. A bug preventing the use of local file copies has been fixed. Language source files are no longer included in packaged apps by default.
For existing apps - This new updater version will automatically update your application to the new 2.0 format. The one exception is the new appicon_128.png within AppInfo, a new 128px PNG icon for future use. Though not required, it is suggested that all publishers include this from now on.
This update of the PortableApps.com Installer allows software publishers to package their apps using our popular tools. Open source projects can use our installer (and all source is included and licensed under the GPL) and release their own PAF files. Freeware publishers can also use our installer with no special permission. Commercial publishers can contact us for permission.
Get Help Packaging for PortableApps.com
If you need help packaging your software in PortableApps.com Format or using the PortableApps.com Installer, just post a note to the Development Forum and we'll help you out.
PortableApps.com Installer / PortableApps.com Format
PortableApps.com Installer is packaged, appropriately, as a PortableApps.com Installer so it will automatically detect an existing PortableApps.com installation when your drive is plugged in. It supports upgrades by installing right over an existing copy, preserving all settings. And it's in PortableApps.com Format, so it automatically works with the PortableApps.com Suite including the Menu and Backup Utility.
Download
The PortableApps.com Installer is available for immediate download from the PortableApps.com Installer homepage. Get it today!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Comments
Very slow
This version of the PAI is pretty slow; it's taking longer to build an installer for Double Commander (a 13.1 MB package) than PAI 2.0 did to build an installer for Iron (a 47.5 MB package). Is there anything I can do about that?
Thanks!
EDIT: I was wrong, it's worse than slow. PAI 2.0.2 keeps getting to around 90% and then hanging. I'm going to have to go back to 2.0 for now.
Bug
Please post a bug report in the forums. Please include more info (does it finish creating the code and then get to compiling), etc. Keep in mind that the progress bar is an estimate. It is not indicative of time remaining after 1 minute. Also, keep in mind that no new releases will be approved on here without the latest installer working for them, so if there is a bug preventing compilation of your app, it's better to get the bug fixed.
Will do
2.0 is having trouble with my package too, so it may not be the PAI. I'll do some more testing, including trying 2.0.2 on packages I've already successfully built with 2.0, and see if I can figure out what's going on. I'll post a report if/when I learn what's going on, and it turns out to be the PAI at fault.
Thanks!
Worked great!
I found no issues on my end yet. But I have only used it twice...