[FEATURE] Please provide a portable version

[Mark-Joy]

Would love to see a portable version. This should not be hard, right?

[clechasseur]

That's already possible. When running the installer, simply choose to install for This user only and you get a local version installed.

[blackcrack]

@clechasseur , is this as a version with an own config.ini with an tsr-dll/exe who adds menu-entrys ? Or is this also writing in the Registry instead in a own config.ini by side of the binary ? Because i ask.. if the program not use an own "config".ini and writes in the regestry , it's imho not really portable.. and leave at end strings who be junks in the registry if it used as portable..

you could a add a if switch, if exist an ./portabe.ini, can you let all configurations read and write from the portable.ini by side of the head binary.. or exe-loader.. as lil' idea .., then is it really portable.. maybe something in this direction.. if it's not..
well, my skills be only html/php, cmd and sh files.. not really directly c or other programming languages..

best

[Mark-Joy]

@clechasseur
There isn't such option on v20.0 Windows 8.1, atleast for me.
Furthermore, portable doesn't mean "current user". It can be portable but is used for entire machine by writing to HKLM(HKEY_LOCAL_MACHINE) registry instead of HKCU (HKEY_CURRENT_USER) registry.
Portable meanning I can run it without installing.
Here is what I expect:

Portable version should save user config to .ini file, so that the config can be re-used in other PCs. Only the ContextMenu is written to registry. It run without installing but providing bellow options:

1. Option to add contextMenu to machine
2. Option to add contextMenu to current user only.
3. Option to clear registry.

As per I understand, there is no need to install it, just writing to registry is enough.

@blackcrack
You can't have it on contextMenu without writing to registry. If we have an option to clear registry (equall to uninstall) then it's fine.

[blackcrack]

@Mark-Joy , but yes, if you work with an injector in the ram and loading dll's( Library ).. because the registry is loading in the Ram, you must only know how you can different things do ;) Or how , do you think can overtake the tweaks so short with AeroTweaker on the Desktop Menu ?, pffhh..
You should be be careful what you claim..
i be more as 25 years in the net.. incl. Bulletinboards over the terminals0X

best

[Mark-Joy]

@blackcrack
yeah yeah keep pffhh...ing .
no one cares about your 25 years.
Imagine a small utility would do what you want, inject its registry to ram, like the developer has nothing to develop except his utility. No one bother doing that. unless you do it.
But again, keep dreaming, man~

[clechasseur]

@blackcrack Please stay on topic. This is not a general forum, it's a support site.

@clechasseur There isn't such option on v20.0 Windows 8.1, atleast for me.

That's probably because you already have a version installed. If the installer detects an existing installation it will default to that installation mode.

Furthermore, portable doesn't mean "current user". It can be portable but is used for entire machine by writing to HKLM(HKEY_LOCAL_MACHINE) registry instead of HKCU (HKEY_CURRENT_USER) registry.

Thanks, then the installer has everything 😉

Portable meanning I can run it without installing. Here is what I expect:

Portable version should save user config to .ini file, so that the config can be re-used in other PCs.

It's currently possible to export the user settings via the Settings app, to a .reg file, which can then be re-imported on other PCs. It might be nice to have an option to consume such a file when installing; food for thought (or feel free to enter another enhancement for it).

Only the ContextMenu is written to registry. It run without installing but providing bellow options:

1. Option to add contextMenu to machine
2. Option to add contextMenu to current user only.
3. Option to clear registry.

As per I understand, there is no need to install it, just writing to registry is enough.

I don't really understand the need for this. "without installing" makes no sense in the context of Path Copy Copy since you need to create registry entries. As you mention, you would need a script to be able to add the necessary entries to the registry (or remove them). We already have that - the installer. What else would we gain by duplicating the installer script in another script?

I will admit though that there isn't currently an option to remove user entries from the registry when uninstalling. Perhaps that's something I could add, although I'm not a fan (because you can't remove them from all users when uninstalling a per-machine installation.)

[Mark-Joy]

I don't really understand the need for this. "without installing" makes no sense in the context of Path Copy Copy since you need to create registry entries. As you mention, you would need a script to be able to add the necessary entries to the registry (or remove them). We already have that - the installer. What else would we gain by duplicating the installer script in another script?

Sorry for my late response. I was caught up with something.

Here is an example of portable app which adds items to Shell Context Menu: HashMyFiles

It has config file .cfg (which is generated if not existed) that saves app's configuration , and executable file .exe.
On a new System/PC, just do: Run the .exe file -> Options -> Check on: "Enable Context Menu".
The config file is already in placed which carries configurations from old System/PC. There's no need to install.
To remove the contextMenu, just uncheck "Enable Context Menu".

Another example is XSearch: download the .zip file
Run the .exe file -> Tools -> Shell Extensions...

[clechasseur]

Sorry for the very late reply, I'm going through the backlog...

I understand how to create an app that can register a context menu programmatically in its UI. However, that's not fundamentally very different from one that does so with an installer. The main feature that's missing from Path Copy Copy would be to save its settings in a local file (INI, YAML, etc.) so that the "installation" can be easily copied to another PC.

I guess I'm just not very familiar with how that would help. I'm reluctant to add something somewhere to register the required COM objects, since it's already done by the installer, so I'd have to be careful not to duplicate things.

I guess I'll leave this open, but I'm still not sure of the use case.