Skip to main content
added 28 characters in body
Source Link
phuclv
  • 28.4k
  • 15
  • 128
  • 252

In PowerShell you can get the Font families in two lines, one to load the .NET reflection and the second actually gets the font families:

[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
(New-Object System.Drawing.Text.InstalledFontCollection).Families
[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
(New-Object System.Drawing.Text.InstalledFontCollection).Families

The outlook looks similar to:

enter image description heresample output

In PowerShell you can get the Font families in two lines, one to load the .NET reflection and the second actually gets the font families:

[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
(New-Object System.Drawing.Text.InstalledFontCollection).Families

The outlook looks similar to:

enter image description here

In PowerShell you can get the Font families in two lines, one to load the .NET reflection and the second actually gets the font families:

[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
(New-Object System.Drawing.Text.InstalledFontCollection).Families

The outlook looks similar to:

sample output

Source Link
Austin T French
  • 10.6k
  • 29
  • 42

In PowerShell you can get the Font families in two lines, one to load the .NET reflection and the second actually gets the font families:

[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
(New-Object System.Drawing.Text.InstalledFontCollection).Families

The outlook looks similar to:

enter image description here