To Documentation Index

TMEdit  The Ultimate App-V Package Editor


Menu: Extensions: Fonts

App-V categorizes aspects of an applications installation into a set of "Extensions", each of which require special processing either during app deployment or during the virtual app runtime.

Fonts are an internally exposed extension that does not affect the external OS during App-V Publishing, but makes them available to applications running in the virtual environment only.

Although the fonts exist as files inside the package, because they are not available outside this can aid in licensing.  Some fonts are licensed on a named user basis and when you install the font on an RDS server you technically owe a license for each user visiting that server.  Additionally, the native OS has an undocumented limit on the number of natively supported fonts (it is around 800, but depends on the size of the fonts), and with virtual fonts the limit is unknown, but much higher than you'll ever need (we have tested 60,000).  

Although fonts are just files, the App-V client needs this extension to trigger it's own virtual Windows Fonts manager to make them available. Virtual Fonts do have a downside; it increases the first launch time for that app to get the fonts loaded in the virtual Windows Fonts manager.   

You can to the following for an Font:

  • View the Font definitions. 
  • You may disable fonts by unchecking the EnableVirt box. It does speed up the initial launch each day for the user if they don't really need the fonts.  
  • You may edit the Path, but then you are responsible for moving the font in the Virtual Files menu.
  • You may edit the DelayLoad setting.  We have not tested to see if this works in the App-V Client or not, but if it does it might be a better launch performance alternative to disabling the fonts altogether. 
  • You may add additional fonts using the + button on the upper right. The dialog will allow you to select multiple font files and a folder for them to be copied to in the package.  By tradition this destination should be VFS\[Windows}]\Fonts folder, but with the virtual Fonts Manager it doesn't matter.