Forum Discussion
Anyone else getting issues with Fonts shared across several packages?
Font file names have been changed but are shared by several MSIX packages. <uap4:Extension Category="windows.sharedFonts"> <uap4:SharedFonts> <uap4:Font File="VFS\Fonts\Font1.ttf"/> <uap4:Font...
I don't think I've tried what you are doing. Have you tried making the font package a "framework" package and then listing it as a package dependency? I have no idea if this would work (because we aren't sure what can be in a framework package and how they actually work), but it might.
I didn't think that Framework packages could have an Applications element in them, i.e. they are just files with no extra XML elements to extend the package functionality. I'll give it a try though and see if it works.
- Oh, right. You can't register the font in the manifest.