[Closed] PAL $PortableAppsBaseDirectory path replace

What's the actual use case to do so is the question? Having it work for drive letters makes a lot of sense so you can move it on a stick between PCs (that's what portable apps were originally about). Having it work when you move an app from one drive to another makes sense (as some people like being able to upgrade from one to another). Having it work as the whole path changes makes sense (cloud drives when synced between PCs do this). But moving just the app up or down directory trees?

On the technical side, the 3 replaces are to handle the 3 use cases listed above. The partial package and drive letter were the two original ones. Base path was introduce for situations where you wanted links to stuff outside your directory to remain intact where the relative path to it changed.

Note that it will work properly if you change the actual base path itself from one thing to another (changing, say, C:\PortableApps to C:\Portable Apps).

We may be able to address this edge case when we incorporate all 3 replaces into a single replace, detecting this situation and skipping one of the replaces.