Forum Discussion
Can we have multiple fixes at the same time
Sleeping_Developer In general, multiple fixups should work, but I would not want to attempt two fixups that attempt to intercept the same Windows API functions.
So for example, the FRF and DynamicLibrary fixups address distinct sets of the API and work well together if needed. The Trace and FRF fixups intercept the same calls (Trace might be a considered a superset), and I would anticipate issues.
I use the trace fixup only to determine what might be required by seeing what the application is attempting to do and how the runtime without the FRF responds. When using the FRF without trace but wanting tracability, you should probably use the debug build version of the FRF. This will output considerable detail to the debug port, which you can view using something like the Microsoft Sysinternals tool DbgView.
If you are creating your MSIX package by repackaging using the Microsoft MSIX Packaging Tool, you can use PsfTooling (free app in the Microsoft Store) to inject the debug version of the PSF into your package. The tool has two shortcuts (PsfTooling and PsfToolingD), one for the release build and the second for the debug build of the PSF.
If building your package as a developer, just include the debug build of the FRF the same way you are doing now, just without the trace.
Dear Tim Mangan ,
I have another question how build msix using debug version of FRF? is there separate library available or configuration?
Thank you,
Vikas
- Tim ManganApr 04, 2020MVP
Assuming you mean build from source, you just ask for the Debug configuration before you buld.
If you were thinking about the NuGet package, I believe they only offer the release build, so you'd be looking at downloading the source and building your own version.
Instructions for using the prebuilt PSF debug in PsfTooling was in a previous response. PsfTooling has two shortcuts, one with the release build and another with the debug.
- tester2420Apr 04, 2020Copper Contributor
Thank you so much for the response, i will build the setup locally.
I am facing one strange issue with Tracefixup and thats where i am trying to explore FRF debug build,
Latest builds of PSF is crashing for TRACE module saying PSFLauncher64.exe have encountered some problem and if i go back to older version of PSF framework, it is not able to match ID's from Manifest file of config.json :(.
Please help me if you have seen this kind of error before.
Kind Regards,
Vikas
- Tim ManganApr 04, 2020MVP
tester2420 There were some crash situations occurring in PsfLauncher that I fixed in a pull request last week that is in the Develop branch. You might want to download that branch and try it.