{"id":4098,"date":"2025-09-19T12:02:03","date_gmt":"2025-09-19T16:02:03","guid":{"rendered":"https:\/\/www.tmurgent.com\/TmBlog\/?p=4098"},"modified":"2025-09-19T12:02:03","modified_gmt":"2025-09-19T16:02:03","slug":"new-in-psf-v-2025-09-19","status":"publish","type":"post","link":"https:\/\/www.tmurgent.com\/TmBlog\/?p=4098","title":{"rendered":"New in PSF v.2025.09.19"},"content":{"rendered":"\n

\"Psf<\/p>\n

The Package Support Framework (PSF) was originally a Microsoft open-source project to help Win32\/DotNet applications run when inside an MSIX Container.\u00a0 TMurgent has taken up the support for the PSF in our own fork here on GitHub<\/a>.<\/em><\/p>\n\n\n\n

Another month, more PSF goodness!\u00a0 This month brings another PSF release with a fix for certain apps, improvements in debugging, and some changes to help us determine if there are some APIs that we need to add intercept fixups for down the road.\u00a0 Here are the details:<\/p>\n

    \n
  1. \n

    MfrFixup.<\/strong> We added additional folders to the mapping list used in MfrFixup that we found were needed in some particularly older applications.\u00a0 These additional folders should be treated as exclusions, as the package should never include files under these folders and any files written should go to the native location to be available from outside of the package.\u00a0 An example would be the ‘Downloads’ folder.<\/p>\n<\/li>\n

  2. Logging Changes.<\/strong> Previously, you would choose either the release or debug binaries of the PSF to affect the logging that the PSF does to the debug console port.\u00a0 In this release we simply the choices, and unless you plan to use a\u00a0 code debugger on your package, you will always just use the release binaries.\u00a0 We added a new configuration option to the config.json file that allows you to set the level of debugging in the json file.\n

    Documentation on these levels are on the Wiki page for Config.Json<\/a>.\u00a0 The default value of 2 provides the same level of debug output as was always available in the prior release builds of the PSF.\u00a0 A value of 4 provides the same level of debug output as the debug builds in the past.\u00a0 But other values are also available as documented.<\/p>\n

    Some formatting of the logging was also cleaned up, which is very useful when using the ParsePsfDebugTool to read the output.<\/p>\n

    Note: It is possible to change the debug level in the config.json file on your test system by using MsixDeploy (part of the free community tools TMEditX Tools) to increase the debug level without having to open the package for edit.\u00a0 On the MSIX tab, select the ‘Installed Packages’ radio button and right click on the package; in the popup menu select ‘Invoke inside Pkg Container’ and ‘Edit Config.Json’ menu.\u00a0 This will update the file in the redirection area of your package.<\/p>\n<\/li>\n

  3. New informational intercepts<\/strong> were added to a few APIs that applications use that we want to gather information about.\u00a0 We will use this information to determine if full intercept fixups are needed over the next 6 months.\u00a0 The APIs that we are worried about are used for Named Pipes, and for COM and ActiveX activations.\u00a0 These informational intercepts are in PsfRuntime for now, but any actual fixup would be either in MfrFixup or a potential new COMFixup.<\/li>\n<\/ol>\n

    This version of the PSF will be included in future releases of several vendor products, including:<\/p>\n