Forum Discussion
Need Help in Applying File Redirection Fixup in MSIX Packaging Tool
Hi Community Members! I need some help here... While trying to use the latest version of the MSIX Packaging Tool I am stuck at applying the file redirection fixup. The requirement is that I have...
Looks like I'm missing out I haven't seen the builtin psf (I've always done it manually).
I will say a couple things.
a) you shouldn't need a file fixup for appdata, writes will already be virtualized into the directory %localappdata%\packages\[packagename]\localcache
What I have seen quite often is if a directory already exists in appdata, it will leak outside the container and reuse the existing folder first.
ex. normal app uses:
%localappdata%\myapp
if that folder already exists, msix will happily use it, and nothing will populate in the localcache folder. (easy solution is to remove, or even move it to the localcache folder).
What you will find out really soon, is that files you put in the container appdata to customize the user config, aren't used/read in the package at all (unless it's normally read from the core install folder). So if you think you are adding in that special json config, or xml, or license file in appdata.. nope it won't read it. What you end up needing to do is have a launch script via psf that copies files from the container and psf does a nice job of at least providing that functionality.
Furthermore, anytime you do need psf for a write permission, it's so much faster (in my opinion) to use ILV
Outside of the <Applications> in the app manifest as direct child element to <Package> you can create an <Extensions> (not to be confused with the <Extensions> UNDER the <Applications>)
section like this:
<Extensions>
<uap10:Extension Category="Windows.InstalledLocationVirtualization">
<uap10:InstalledLocationVirtualization>
<uap10:UpdateActions ModifiedItems="keep" DeletedItems="reset" AddedItems="keep" />
</uap10:InstalledLocationVirtualization>
</uap10:Extension>
</Extensions>
bit for info here:
https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-uap10-updateactions
I will say a couple things.
a) you shouldn't need a file fixup for appdata, writes will already be virtualized into the directory %localappdata%\packages\[packagename]\localcache
What I have seen quite often is if a directory already exists in appdata, it will leak outside the container and reuse the existing folder first.
ex. normal app uses:
%localappdata%\myapp
if that folder already exists, msix will happily use it, and nothing will populate in the localcache folder. (easy solution is to remove, or even move it to the localcache folder).
What you will find out really soon, is that files you put in the container appdata to customize the user config, aren't used/read in the package at all (unless it's normally read from the core install folder). So if you think you are adding in that special json config, or xml, or license file in appdata.. nope it won't read it. What you end up needing to do is have a launch script via psf that copies files from the container and psf does a nice job of at least providing that functionality.
Furthermore, anytime you do need psf for a write permission, it's so much faster (in my opinion) to use ILV
Outside of the <Applications> in the app manifest as direct child element to <Package> you can create an <Extensions> (not to be confused with the <Extensions> UNDER the <Applications>)
section like this:
<Extensions>
<uap10:Extension Category="Windows.InstalledLocationVirtualization">
<uap10:InstalledLocationVirtualization>
<uap10:UpdateActions ModifiedItems="keep" DeletedItems="reset" AddedItems="keep" />
</uap10:InstalledLocationVirtualization>
</uap10:Extension>
</Extensions>
bit for info here:
https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-uap10-updateactions
In my VFS the issue is that I don't have localappdata folder instead it says only appdata so it is not reading those files from there. I tried copying those files manually to the "AppData\Local\Packages\App_Name\AppData" but still it is not reading the files... Any suggestions?
- Have you tried setting the entry point on your main executable for the shortcut as per the new MSIX Packaging Tool GUI allows, as I had a similar experience with wildcards as per your advanced installer example until I combined copying my user settings in VFS\Profile using a Start script.
