{"id":3113,"date":"2020-06-18T10:00:00","date_gmt":"2020-06-18T14:00:00","guid":{"rendered":"https:\/\/www.tmurgent.com\/TmBlog\/?p=3113"},"modified":"2020-06-17T19:00:06","modified_gmt":"2020-06-17T23:00:06","slug":"psftooling-3-8","status":"publish","type":"post","link":"https:\/\/www.tmurgent.com\/TmBlog\/?p=3113","title":{"rendered":"PsfTooling 3.8"},"content":{"rendered":"\n

With the updates to the MSIX Package Support Framework<\/em> for June 2020, described in https:\/\/www.tmurgent.com\/TmBlog\/?p=3095<\/a>, I added a new type of fixup to the PSF, RegLegacyFixups.<\/p>\n\n\n\n

Version 3.8 of PsfTooling<\/a> is now available up in the Microsoft Store. This free tool is used alongside the Microsoft MSIX Packaging Tool<\/a> to add and configure the PSF into your recaptured package.<\/p>\n\n\n\n

Version 3.8 continues the trend of helping automate bringing in the PSF and configuring it. In addition to integrating the latest PSF, including the new RegLegacyFixups <\/em>module that you can read about in the prior blog article<\/a>, the Debug build includes the WaitForDebuggerFixup <\/em>not previously included in the tool. <\/p>\n\n\n\n

WaitForDebugger is used by people that want to run a code debugger and adding this fixup pauses the targer process right after PsfRuntime is injected into it. This allows time to attach the debugger into the app. Only people with souce code to either the PSF or target app are interested in this.<\/p>\n\n\n\n

Due to the increased number of fixups, the fixup configurations have been reorganized a bit to make it less confusing to use. The internal help has been updated (click on the small “i” icon for information) that provides a decent overview of the workflow that you should use and what all those things are.<\/p>\n\n\n\n