Find a way to build and run Windows Terminal from the commandline #3022

Closed
opened 2026-01-30 23:11:02 +00:00 by claunia · 2 comments
Owner

Originally created by @zadjii-msft on GitHub (Jul 31, 2019).

Since #1987, our SxS manifest is auto-generated, so it's certainly possible to run the terminal unpackaged again. However, we need the resources.pri that's only generated by building the CascadiaPackage project. Ideally, we'd be able to rebuild the terminal code (with bx, #2168), and launch it using openterm. We need to figure out a way to get openterm to build the appx's resources.pri for us, and not re-build every time openterm is called.

Originally created by @zadjii-msft on GitHub (Jul 31, 2019). Since #1987, our SxS manifest is auto-generated, so it's certainly possible to run the terminal unpackaged again. However, we need the `resources.pri` that's only generated by building the CascadiaPackage project. Ideally, we'd be able to rebuild the terminal code (with `bx`, #2168), and launch it using `openterm`. We need to figure out a way to get openterm to build the appx's resources.pri for us, and not re-build every time `openterm` is called.
claunia added the Issue-TaskResolution-DuplicateProduct-MetaArea-Build labels 2026-01-30 23:11:02 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Jul 31, 2019):

This is a duplicate of #926!

@DHowett-MSFT commented on GitHub (Jul 31, 2019): This is a duplicate of #926!
Author
Owner

@zadjii-msft commented on GitHub (Jul 31, 2019):

Oh my god it is

@zadjii-msft commented on GitHub (Jul 31, 2019): Oh my god it is
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3022