Respected Sir/Madam, I want a small Information from You. Is there posibility to make Portable Apps to Standard Installation. i.e. I want a standard Installation Programme from Portable Apps.
New: DesktopSnowOK (Jan 6, 2025), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads Nov/Dec/Jan!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Just go to the original author's website and download the installer.
I don't understand what advantage you think there is from breaking a portable version of an app.
Please help me to understand.
Making some assumptions, I would believe they are referring to the ease of updating en-masse.
If that being the case, then maybe they could take a look at a service such as Ninite, where they bundle up many common applications into their own installers, which will perform a traditional install but without the associated fluff or bloatware.
You can then simply run the downloaded installer to check for updates.
Not quite as integrated as the PA platform, unless you want to fork out money for the paid version.
If at first you do not succeed, use more sticky tape.
Can a portable app be used exactly as their non-portable counterparts?
Simply put, can I load extensions, plugins, etc into a portable web browser downloaded from here, through PortableApps.com launcher?
What are the pitfalls of updating a portable app from within the app itself if prompted?
PortableApps can be used exactly like the non-portable version with some considerations:
Regarding browser extensions and plugins, it is up to the individual extension/plugin as to whether it behaves the way it should. A badly programmed extension may not be portable, and plugins often aren't portable, but there is no way to tell without installing them and trying.
Whether you use in-app updates is up to you. Most of the time they are fine to use, but if the base app changes the way it stores settings or changes the name of a filename or registry entry then it could potentially break portability, or (at worst) break the app completely.
?!
So... the stub file that loads the real file does some sort of magic?
I think this needs to be in bold somewhere on the homepage.
Also, while I didn't actually do that (to my knowledge, at least my current shortcuts are correct), my SeaMonkey Portable has files within my users/me/appdata/roaming/mozilla folder...??
This might be because I've loaded themes into SeaMonkey, as well as extensions... but I cannot find any CSS files in my portable folders...? I made a thread about this...
Depends on the base app as to what AppNamePortable.exe does. It is customized to what each individual app needs, whether it be environment variables, command line options, files/folders/registry entries in particular places, as well as handling things like language switching when used with the PortableApps Platform and updating drive letter/folder options that the base app needs as the drive is moved around.
If SeaMonkey has files anywhere other than within the SeaMonkeyPortable folder while it is not running, then you have been using it non-portably.
I would assume being a Mozilla app that SeaMonkey has profile redirection much like Firefox and Thunderbird. As such if it had been running portably all your user data would have been stored within SeaMonkeyPortable/Data, including themes and most (if not all) extensions.
didn't mean to hijack a thread...
but I renamed those folders and all is well now.
I guess one of the times SeaMonkey crashed it didn't move the contents...
What I did was rename the folder and start up SeaMonkey. I checked everything out and it all works as expected. Safe to delete, so deleted. It did not reappear after exiting SeaMonkey. It took a few seconds for the contents to 'flush' after exit, but it did.