Forum Discussion
Can we have multiple fixes at the same time
MicrosoftHey Sleeping_Developer ,
I took a look at your supplied Json.config file. First off there are no json syntax errors, that is good.
Besides the syntax I see you declared fixups for the same process, was that expected?
The syntax for the config sections look good as well. Tell me, for the FRF work fine on it's own?
Also, to answer your question, it is okay to declare multiple fixups for the same process.
Darren_Hoehna Thank you for the reply,
1)File redirection fix up didn't work for me
2)Yeah, i am trying to applying both fix up for the same process, is there any problem if i do so ?
Please help me if there is another way to apply fix ups.
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.
Tim Mangan Thank you so much for the information!
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
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.
- Darren_Hoehna
HeySleeping_Developer ,
Your file redirection is not working? Well, we need to make sure FRF works before moving to adding a second fixup.
First, I want to make sure you have all the dll's and exe's in your app folder. You will need
1. PSFLauncher64.exe
2. FileRedirection64.dll
3. PsfRunDll64.exe
Those three dll's are needed to have PSF run correctly.
Next, the configuration. It looks like you want all file operations under ProgramFilesX64\MyPackage\* to be redirected. PSF should redirect all file operations to that location. If you have the three binaries mentioned in step 1 but PSF does not redirect the files I'll need to dig deeper.
You are absolutely correct about two or more fixups. But, you don't need to declare two process nodes. You can put both fixups under the same process. You can remove the second "MyPackage64" executable node.
Darren_Hoehna Thank you for the help!it worked well! Apologies for late reply!
