Skip to content

Conversation

@DHowett
Copy link
Member

@DHowett DHowett commented Jun 21, 2022

These files are vestigial, because we are also shipping (either as loose
files or embedded in resources.pri) precompiled xbf/xaml binary format
files.

This saves us almost 500kb on disk.

Fixes #11687

Validation

I ran a local build and saw that it produced a working Terminal, packaged
and unpackaged.

These files are vestigial, because we are also shipping (either as loose
files or embedded in resources.pri) precompiled xbf/xaml binary format
files.

This saves us almost 500kb on disk.

Fixes #11687
@ghost ghost added the Issue-Question For questions or discussion label Jun 21, 2022
@zadjii-msft zadjii-msft added this to the EIM Summer 2022 milestone Jun 21, 2022
@DHowett DHowett merged commit 0b97c7b into main Jun 21, 2022
@DHowett DHowett deleted the dev/duhowett/noxaml branch June 21, 2022 18:37
@WSLUser
Copy link
Contributor

WSLUser commented Jun 23, 2022

Are we able to modify these xbf files? For those of us who don't agree with Win11 style UI and revert to the Win10, the Xaml files were pretty convenient way of doing so.

@zadjii-msft
Copy link
Member

... I don't think the .xaml files in the package were ever being used. The Terminal should have always been directly referencing the pre-compiled .xbf's. Were you successfully modifying the Terminal's xaml by manually editing the xaml files before? If so - how?

@DHowett
Copy link
Member Author

DHowett commented Jun 23, 2022

Yeah, that's quite surprising. There's a number of issues with that approach.

  1. XAML prefers xbf files, and will use them preferentially
  2. Terminal's xbf files are all bundled inside resources.pri, so it never hits the disk to even look for xaml files.
  3. Changes made to the code behind each XAML file make them mutually incompatible with the Windows 10 styled versions, in many cases.
  4. If you get weird crashes when you do this, you risk filling up our crash reports with unsupportable/non-actionable chaff we have to filter through 🙂

@DHowett
Copy link
Member Author

DHowett commented Jun 23, 2022

(I totally get why you feel that way, btw, and I wanted to thank you for sharing your use case!)

DHowett added a commit that referenced this pull request Jun 30, 2022
These files are vestigial, because we are also shipping (either as loose
files or embedded in resources.pri) precompiled xbf/xaml binary format
files.

This saves us almost 500kb on disk.

Fixes #11687

Validation
----------
I ran a local build and saw that it produced a working Terminal, packaged
and unpackaged.

(cherry picked from commit 0b97c7b)
Service-Card-Id: 83425307
Service-Version: 1.14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Issue-Question For questions or discussion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Terminal XAML files should be in binary (.xbf) format for improved performance

5 participants