Portable App Development

I've looked around the forums, and generally it can be seen that PortableApps Launcher handles the registry in a few steps.

When the application is launched, it checks if there is anything existing in the targeted registry key and backs it up, then the portable app will write its own key in. When the application is closed normally NSIS has the time to backup the written registry key and restore the original key.

However, if NSIS is terminated, then the registry is not handled correctly and the app will clean up on next startup.

So my question is, what happens if you run the local non-portable application before you restart the portableapp?

does anyone know if their is a way "script" for Launcher.ini
that will block the .exe from conecting to the internet.

I know how to make Rules with a Batch file. but their goes the portable,,
if i do this. and also every time it would be Ran it would just keep
adding to the rules...not good.

thanks jedione

I'm not sure where to submit apps once they have been made, but this looks like the best place. I made a USB friendly version of Git Portable, which involves a .bat file changing run time settings. Can someone can please lift this from me and put it on the app directory for other users? Thanks!

Note: Git is the best version control system and it is a must have for collaborative development.

Link: https://dl.dropboxusercontent.com/u/36287163/Git.7z

Edit: It's uploading slowly so if you don't get the download check later.

Hey Guys Been Making a lot of my own Personal non Realease
PAF files from Apps That I own...And till now I have always
used HKU's as HKU=HKCU\whatever, then a cleanup. as it says in the
Manual. But now I am finding with this one App that it has to be
in the HKU for it to work Registerd. will not work edited for the HKCU.
I did Read that this can not Be written To...IS this Correct..
am I missing Somthing. if any one has a hint or sugestion that
would be Great. Or am I SOL. Peace Jedione

I've looked through the forums for an answer but couldn't find any recent discussions (most of the posts were several years old).

I understand that the current policy is not to officially support .NET apps. They are available under a separate download section. I understand why this decision was taken (http://johnhaller.com/jh/useful_stuff/dotnet_portable_apps/) and it made sense at the time (that page was last updated in 2010).

I saw that many apps require %PAL:PortableAppsBaseDir% to replace paths stored in settings files. However why it will not work if I only use %PAL:Drive% and %PAL:LastPackagePartialDir% to replace the old paths (why we have to add %PAL:PortableAppsBaseDir% to ensure paths are modified correctly)?

Recently I found a program in development that you can enter the settings for the app, and it will create a folder with all the correct formats for that app. But, I deleted it and now I can't find it. I can't find the link either, someone please help find the link for me...

Hey Cody, I got a question for you. I noticed in your unsupported directory, a launcher for CCEnhancer. As I just received permission from the author to make a launcher for this available, do you mind if I just use your launcher and update it to the newest version? I figured that would be quickest, but I wanted to ask first.

So, I wanted to make a new portableapp for the first time in 6 months or so.
Registry is bugging me, so I decided to create a SSCCE.

I created HKEY_CURRENT_USER\Software\AAA in the registry, to mess with. Under that key, I added the value "test" with value 1. I backed up the key, named it AAA.reg and moved it to \Data\settings.

Next, I made a small portableapp, filled the appinfo.ini and help.html with normal values, nothing important. AAAPortable.ini in \App\Appinfo\Launcher looks like this:
[Launch]
ProgramExecutable=AAA\AAA.exe


Assuming that an app saves its settings in a file *.dat. Especially may be saved the changes with respect to drive-letters and languages in this file *.dat. Because of the difficulties regarding the access to this *.dat file, there are now basically 2 options.

1. Removing of the file *.dat

Firstly I can remove this file *.dat. Afterwards I look, where the app now stores its settings. Now I start the development of a portable version of the app.

2. Access to the file *.dat