Forum Discussion
Appdata roaming and local in package
I ran through the behaviour with W10 1909 and 1.2019.1220.0 yesterday and found that the problem has not been fixed yet.
ā
Ah, a Service would be a different animal indeed. My comments were directed to the portions of the app that are running under the container.
My belief (possibly wrong in which case John should correct) is that while the MSIX package can be used to deliver the Service, the Service itself runs outside of the container, and thus is not able to use any VFS layering, or the PSF fixes, and probably also the containerized registry from the app package.
A full review of containerized package dependencies that the Service has needs to be understood, and I would recommend that you explain those needs to Microsoft. Non VFS files should be visible just by the Service understanding the different installation folder. Files in the VFS portion could be copied out to the old native locations via a first run script, although since you are the developer knowing the installation path it might be easier to modify your Service (or service installer) to record where to find the files (which would be a VFS/LocalAppData folder off of the installation root) in a non container registry location. I have no idea what to do about any need of the service to use the app registry in this situation.
But this is the initial attempt at services so maybe there will be room for improvement as Microsoft becomes aware of what the full sets of needs are.