starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Package Building Guide #1484

New Issue
Closed
opened 2026-01-30 22:28:28 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:28:28 +00:00
Owner
Copy Link

Originally created by @LanceaKing on GitHub (Jun 3, 2019).

Instructions

Step 1: Clone the repository from github

To clone the repository, you just need to run the following commands.

git clone https://github.com/microsoft/terminal.git
cd terminal
git submodule update --init --recursive

Then install the prerequisites written in README.md .

Step 2: Find the publisher name

Check Package-Dev.appxmanifest which located in src\cascadia\CascadiaPackage, and you can find something like this:

<Identity
  Name="WindowsTerminalDev"
  Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"
  Version="0.0.1.0" />

Copy the "Publisher" attribute CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US .

Step 3: Create a package signing certificate

Open the "Developer Command Prompt for VS 2019" in start menu, and run following commands with the publisher name:

MakeCert -n "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" -r -h 0 -eku "1.3.6.1.5.5.7.3.3,1.3.6.1.4.1.311.10.3.13" -sv CascadiaPackage_TemporaryKey.pvk CascadiaPackage_TemporaryKey.cer
Pvk2Pfx -pvk CascadiaPackage_TemporaryKey.pvk -spc CascadiaPackage_TemporaryKey.cer -pfx CascadiaPackage_TemporaryKey.pfx

If asking for password, click "None".
Then install "CascadiaPackage_TemporaryKey.cer", and store the certificate in Trusted People.

Step 4: Build

Copy "CascadiaPackage_TemporaryKey.pfx" to src\cascadia\CascadiaPackage .
Open "OpenConsole.sln" (Don't need to retarget), right click the "CascadiaPackage" under "Terminal" in solution explorer, and then click "Store->Create App Packages...".
Select "Sideloading" and uncheck "Enable automatic updates", and then click "Next".
Change settings if you like, and click "Create".

Step 5: Install

When package building finished, the package and certificate are under src\cascadia\CascadiaPackage\AppPackages\CascadiaPackage_0.0.1.0_Test.
And then you can double click to install it. 👍

Originally created by @LanceaKing on GitHub (Jun 3, 2019). ## Instructions ### Step 1: Clone the repository from github To clone the repository, you just need to run the following commands. ```cmd git clone https://github.com/microsoft/terminal.git cd terminal git submodule update --init --recursive ``` Then install the prerequisites written in `README.md` . ### Step 2: Find the publisher name Check `Package-Dev.appxmanifest` which located in `src\cascadia\CascadiaPackage`, and you can find something like this: ```xml <Identity Name="WindowsTerminalDev" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" Version="0.0.1.0" /> ``` Copy the "Publisher" attribute `CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US` . ### Step 3: Create a package signing certificate Open the "Developer Command Prompt for VS 2019" in start menu, and run following commands with the publisher name: ```cmd MakeCert -n "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" -r -h 0 -eku "1.3.6.1.5.5.7.3.3,1.3.6.1.4.1.311.10.3.13" -sv CascadiaPackage_TemporaryKey.pvk CascadiaPackage_TemporaryKey.cer Pvk2Pfx -pvk CascadiaPackage_TemporaryKey.pvk -spc CascadiaPackage_TemporaryKey.cer -pfx CascadiaPackage_TemporaryKey.pfx ``` If asking for password, click "None". Then install "CascadiaPackage_TemporaryKey.cer", and store the certificate in Trusted People. ### Step 4: Build Copy "CascadiaPackage_TemporaryKey.pfx" to `src\cascadia\CascadiaPackage` . Open "OpenConsole.sln" (Don't need to retarget), right click the "CascadiaPackage" under "Terminal" in solution explorer, and then click "Store->Create App Packages...". Select "Sideloading" and uncheck "Enable automatic updates", and then click "Next". Change settings if you like, and click "Create". ### Step 5: Install When package building finished, the package and certificate are under `src\cascadia\CascadiaPackage\AppPackages\CascadiaPackage_0.0.1.0_Test`. And then you can double click to install it. :thumbsup:
claunia added the Issue-QuestionResolution-By-DesignProduct-TerminalArea-Build labels 2026-01-30 22:28:28 +00:00
claunia commented 2026-01-30 22:28:29 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 3, 2019):

Thanks for taking the time to produce this guide. We'll be evaluating our deployment strategy in the coming weeks. @bitcrazed

@DHowett-MSFT commented on GitHub (Jun 3, 2019): Thanks for taking the time to produce this guide. We'll be evaluating our deployment strategy in the coming weeks. @bitcrazed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Build Issue-Question Product-Terminal Resolution-By-Design
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1484
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?