4 ms·

Is there something more granular than "File system access" or not? I would like for apps to have their own temp/cache and optionally access to common files. Hav

Is there something more granular than "File system access" or not? I would like for apps to have their own temp/cache and optionally access to common files. Having to do all or nothing significantly curtails the utility.

charcircuit 3y ago
It already is granular. The "File system access" setting is unrelated to what this article is talking about. That setting is for the broadFileSystemAccess capability for UWP apps.
mike_hearn 3y ago
MSIX already provides that. All apps run in a very lightweight "sandbox" that virtualizes file access to the user's AppData directory. Writes inside it are redirected to a package-private location that's blown away on uninstall. Same for registry writes. It means the OS can cleanly and immediately uninstall such packages. Temp is also virtualized in the same way, although Conveyor devirtualizes it in some cases due to a Windows kernel bug. This is just intended for keeping the system clean. Your app can devirtualize locations in AppData by requesting it in package metadata, if you need to modify files belonging other apps for example, see: https://conveyor.hydraulic.dev/13.1/configs/windows/#virtualization https://conveyor.hydraulic.dev/13.1/configs/windows/#virtual...
- actionfromafar 3y ago
  Huh, interesting, I will have to reconsider MSIX then. It sounds very neat.