Single MSIX Package for Different Environments

Like Tim already mentioned, the MSIX Helper tool is designed as an alternative for the PSFLauncher for adding basic script tasks before and after the program is started. For now, there is no dll injecting possible to manipulate the behaviour of the application itself. However, it is for example possible to copy the program files outside the original (non writable) MSIX package location (like the %USERPROFILE% or %TEMP% location) when starting the application so the program will run from a writable location if needed. Keep in mind that although the program can be started using the MSIX entry points from the start menu or filetype associations, registry information and the VFS inside the MSIX package will not be accessible when the application is started outside the MSIX container. I have used this for the KeePass application to make this work when it is delivered as an MSIX package. KeePass is known not to work when the program is started from the MSIX container location (C:\Program Files\WindowsApps) but will work perfectly when it is (temporarily) copied to (and started from) a location like %TEMP% or %USERPROFILE%. This can be done using the basic script actions as described in the MSIX Helper documentation.

Pollewops Regarding Ferry's tool, It looks like a exe launcher controlled by an ini file.  Like by old ScriptLauncher program we used for App-V, it is simple to use but does not lend itself to the dll injections required if you need PSF injections.  You would have to manually apply it to the package, including changing out the shortcuts.