You are here

Portable App Development

Discuss portable app development and modification of existing apps.

Deploying PortableApps via PowerShell

Submitted by roysubs on October 5, 2022 - 7:28am

I notice that PortableApps executable containers can simply be unzipped, but also possibly there are switches to do it according to your standards, so I would like know the best way to do this in PowerShell. i.e. I want to *silently* deploy some app:

$7z = "D:\MyDownloads\7zipPortable.exe"
if (Test-Path $7z) { & $7z [whatever-switches-required] [install-directory-of-my-choice] }

Would appreciate any advice on the correct / most efficient way to do this for multiple packages?

Support passing launching command line switch/parameter in appinfo.ini

Submitted by Mark888 on September 28, 2022 - 12:12pm

Hello,

While some kinds of command line parameter are supported under [Associations] section such as: FileTypeCommandLine, FileTypeCommandLine-extension, ProtocolCommandLine, SendToCommandLine, ShellCommandLine; the command line switch/parameter for launching the app is poorly supported. It is only supported via myAppPortable.ini which is not so obvious and only support for main App.

My suggestion is something as below:

appinfo.ini
[Control]
Start=AppNamePortable.exe

Only delete the myappPortable symlink when uninstall

Submitted by Mark888 on September 28, 2022 - 11:39am

Hello,
I have myAppPortable symlink (directory symlink) placed under PortableApps folder.
When I choose uninstal myApp from PortableApps platform, it deletes the contents (files and folders) inside the symlink directory.

Not sure if it is a bug.
But please when uninstall myApp, only delete the symlink, not the contents. Or provide option to only delete symlink.
Should also take care of other symlinks if any present in myAppPortable.

Take certain actions based on the number of NSIS instances running

Submitted by SimonGeek on September 1, 2022 - 4:57am

Hi, I am trying to take certain actions based on the number of NSIS instances running.
The main reason is that if there are two instances of the same executable the data created is overwritten

I asked in the NSIS forum but the code provided doesn't work. I wanted to put the code in multiple sections, the one provided by the NSIS forun can only be used once.

If there is only one instance does it perform an action, if there are two or more does it perform another

QEMU or VirtualBox?

portablepro's picture
Submitted by portablepro on August 16, 2022 - 8:18pm

Which is your favorite? Especially via been portable?

Sorry I forgot to mention that both Softwares are available in a "portable format"

Qemu does by definition to be portable - VirtualBox still trying to only be installed, but told to
be installed portable by no ways.

HTH

Different executables for different Windows versions?

Submitted by Fayne Aldan on August 14, 2022 - 4:40pm

Hello. I want to make my portable app change ProgramExecutable based on the version of Windows. I tried to this in Custom.nsh:

${SegmentFile}

${SegmentInit}
    ${If} ${AtLeastWin110}
        ${SetEnvironmentVariablesPath} FullAppDir $AppDirectory\PolyMC
    ${Else}
        ${SetEnvironmentVariablesPath} FullAppDir $AppDirectory\Legacy
    ${EndIf}
!macroend

But it seems I can't use the environment variable in ProgramExecutable. Any idea how I'd accomplish this? Thanks.

Help with creating a PortableApps version of Tabby

Submitted by wolfferine on August 5, 2022 - 4:12am

Hi,

I am new at this, and so would very much appreciate the help from the community - i am trying to create a portableapps (paf) version of Tabby.
I created the appinfo.ini:


[Format]
Type=PortableAppsFormat
Version=3.7

[Details]
Name=Tabby PortableApps
AppId=TabbyPortable
Publisher=Wolfferine
Homepage=
Donate=
Category=Internet
Description=Tabby - a terminal for the modern age
Language=Multilingual

Pages