Currently, Font Family Resources generate unexpected and potentially problematic paths in the generated XAML.

Repro Steps:

1) Create a Studio Project Containing a MainPage.xaml
2) At the Project Root, create an 'Assets' Folder containing a 'Fonts' Subfolder, and place within it any font file within it in Windows Explorer. (A system font can easily be copy-pasted from: C:\Windows\Fonts )

3) Within MainPage.xaml, introduce a TextBlock to the Page from the Assets Panel.
4) With the TextBlock selected, navigate to its Properties Panel, and from the 'Family' Property select the font included in the Project from Step 2) (prefixed by a '#' character)
5) Once the font selected from, click on the Family's 3-Dot menu, and select 'Convert to Resource' and save the Resource in the GlobalResources Dictionary.

6) Open GlobalResources in VS Code.

Observe how the FontFamily's Resource Path includes the "studio:" scheme at the beginning of the path.

Expected Results: Allegedly, Font Family Paths should be absolute, starting with the Namespace, and not the 'scheme'.