Fast testing
Hand a build to a tester without forcing a normal installation workflow first.
Create a portable Windows package without turning it into a second deployment project.
InstallerLab v3 keeps the Portable workflow for compatible Application projects: choose the source executable, source folder and output, then package the distribution for use without a traditional installer. B4J projects get a dedicated toolchain-aware Portable workflow.
Portable EXESource folderMain executableIcon / versionB4J Portable
Why developers want a Portable build
USB and toolkits
Keep utilities together in a portable distribution when a traditional installed application is unnecessary.
Side-by-side builds
Portable packages can simplify testing different versions without changing a normal installed copy.
Clean developer handoff
Package the runtime files your application actually needs instead of asking another developer to reconstruct your environment.
One packaging workspace
Keep Setup EXE, MSI, Bundle and Portable choices in InstallerLab rather than adopting another tool for each format.
Specialized B4J path
For B4J, InstallerLab reads project packaging properties and uses B4JBuilder/B4JPackager11 before applying its own distribution layer.
Generic Portable workflow
- Select the application's main EXE.
- Use the executable's folder as the application source.
- Choose an output location outside the source folder.
- Optionally provide icon and version information.
- Generate the portable package.
B4J Portable workflow
- Select the .b4j project.
- Read supported
#PackagerPropertyvalues. - Use the configured B4J/JDK toolchain.
- Compile and create the standalone runtime.
- Add InstallerLab's launcher/distribution layer.
Portable packaging FAQ
Is Portable creation free?
Portable package creation is unlocked by the optional supporter/PRO activation. The core InstallerLab installer workflow remains free.
Can Office Add-in or QGIS Plugin projects use Portable?
No. InstallerLab v3's Smart Build Targets keep Portable for compatible Application projects; Office Add-in and QGIS Plugin projects use MSI and Bundle.
Is the downloadable InstallerLab Portable EXE the same as the PRO feature?
No. The portable edition of InstallerLab itself is a download format for running InstallerLab. The PRO feature is the ability to create portable packages for other applications.
Does a B4J portable require Java on the target PC?
A correctly generated standalone B4J package includes the required runtime pieces, so the end user does not need a separately installed global Java runtime.
Need both installed and portable editions of your app?
InstallerLab keeps the application definition and distribution decisions together while v3's project-aware UI prevents Portable from being offered where its semantics do not apply.