RW access to VFS in MSIX packages

Occasional Contributor

Hi all,

 

I need to give RW access to VFS in MSIX packages. In App-V, we had one checkbox which was responsible for this. However, in MSIX we don't have any such provisions.

Also, I would prefer if we can give the access in general to all folders of the package rather than being specific to the folder name and file name required.

Please let me know if anyone has achieved this.

5 Replies
The PSF FileRedirectionFixup was created for this purpose.
Hi Timothy,
Thanks for responding, I could find blogs regarding this. However, in the article, they are asking to specify the particular file extension which is getting created on run time, but what if there are multiple files/ folder structure being created at different locations? Can we give a RW access to the complete VFS structure?

@SJamal85

The wiki documentation Fixup: FileRedirectionFixup · TimMangan/MSIX-PackageSupportFramework Wiki (github.com) has a sample configuration file that probably works for you. 

 

The two entries under `packageRelative` provides pretty much what App-V does with that checkbox of the sequencer; redirect any file request that is in the package area (PVAD or VFS) to the redirection area (except for standard executable file formats).

 

The known folder entries below are optional and allow you, for example, to have a VFS folder for documents inside your package but using the exclusion allows the app to write files to the native documents folder.

@TIMOTHY MANGAN Hi Timothy,
I tried your solution. However, now when launching the application, it is not throwing initial error also and nothing seems to be happening.

I am attaching the config.json file along with screenshot of my PSF files added to the package.

Let me know if I am missing something here. IT doesnt look like Config file format  issue else it would have given that error.

Appreciate all your help.

@SJamal85 I am traveling, but at quick glance the json looks good as a start. Test with SysInternals DebugView running before you launch. You will see a trace that should show if the app was started and if the FRF was injected. 

 

If not, you have a packing error. If nothing pops out in that log, then it is an app issue. Latter case, using the Debug build of the PSF will show details of what the FRF is doing, and process monitor is useful also. 

 

About 30% of apps work well out of the box, 30% can be tweaked, and 30% do things we cannot yet fix, so no guarantees you can solve it.