


* The setup is universal: it allows both standard and portable installation. ex2 is launched with additional command line parameters, which make it behave like a portable version (use the. exe is a tiny launcher, and it uses the standard method of starting a new process to launch.

We use this layout and our special installer for lots of reasons: If there is a command parameter we can pass, we could eliminate the move back and forth and our launcher would just serve as a portable/relative glorified shortcut to start your app with the command line parameter and then immediately exit. The data file is moved back and forth to your app (7+TaskbarTweakerPortable\App\7+ Taskbar Tweaker) and to the Data location (7+TaskbarTweakerPortable\Data) by our launcher that would then wait for your main and secondary EXEs to exit. Your existing directory layout can stay within ours. Here is as far as I'd gotten in my quick test to serve as a good example starting point: Possibly by injecting into explorer.exe? (which crashed on my Windows 8.1 box) You may also find increased false positives due to running an EXE that doesn't end in either EXE or BIN. I'm not sure how your main EXE calls the secondary one but it's somehow breaking out of the launcher. I tried to put together a quick example of showing how it moves the files, but I'm not sure if PAL can handle the switch to the odd.
