The Package Support Framework (PSF) was started by Microsoft as an Open Source Project to help Win32 and .Net Framework based software operate in the new MSIX Container runtime, however the latest changes are now made in my own fork at https://github.com/TimMangan/MSIX-PackageSupportFramework/tree/develop
November brings new changes to the PSF, and while some much needed improvements are part of the mix, it also affects what needs to be added to the package and how some things work.
The primary changes in this release are:
- Processes from exe files not located inside the package, whether listed as the executable in the config.json file, or a child process running inside the container under the PSF, generally will now run inside the container. Previously these ran outside of the container if the exe file itself was not in the package.
- CMD/BAT files when executed by the PsfLauncher will now attempt to run inside the container. To work, this requires an updated client OS (21H1 or above) and inclusion of a new PSF supplied PowerShell wrapper script to run your cmd/bat file. For older clients you can modify the PSF supplied wrapper script to not attempt the injection back into the container or use the prior Psf Release.
- Other file types that you want to launch via PsfLauncher (PDFs, Doc files, CHM files, etc) will now attempt to run inside the container. To work, this requires an updated client OS (21H1 or above) and inclusion of a different new PSF supplied PowerShell wrapper script to run your FTA file. The Launcher runtime will determine the default action for the local FTA and attempt injecting that program back into the container. The the program is associated with a Console program, then it will run outside of the container anyway, but windows programs will run inside. For older clients you can modify the PSF supplied wrapper script to not attempt the injection back into the container or use the prior Psf Release.
- Fixes are made to the FileRedirectionFixup for issues seen in certain applications as complications of the September re-write.
For more information on the launching changes, the PsfLauncher readme.md documentation has been updated.
Updates to PsfTooling and TMEditX to include this version are forthcoming and will be announced in this blog when ready.
