Portable App Development

Because of old habits mostly I have since the beginning named my portable apps in the form of PortableFirefox (as an example). The portable apps platform nor the manual updater does not accept this right away but wants the form FirefoxPortable (no space). If I don't use this form the platform will not update the apps.
Is there any way I can "fix" this as I would like to keep my naming in the form of PortableFirefox or at least PortableFirefox?

Hi, I noticed that the PA.c Launcher allows you to configure a custom icon to be associated with files through the FileTypeIcons section. Is it possible to implement this function in a custom NSIS script without using the PA.c Launcher? Thank you

really... where are simple .zip files?^
as if having "installers for portable" (which is nonsense on its own... but tolerated while it was optional, which does not seem to be anymore) but who was the [slur removed by mod JTH] person that tought it was a good idea to make the installer automatically select between 32bit and 64bit?

so now its impossible to "install the 32bit" on 64bit windows?????

really.. i dont think it can get any more dumb than that luls...

I'm working on making a Java program run in a PortableApps Launcher (specifically Ghidra). The problem I see so far is that this program specifically needs to be run in a JDK environment, and doesn't work with just JRE.

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?

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

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.

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

Driver virtualization - Done
Embedding - Done

HTH FYI

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