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

Deploy Terminal to Microsoft Store (either as beta/Insider builds) #1059

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

Originally created by @jcoutch on GitHub (May 14, 2019).

Would it be possible to release preview/Insider builds of Terminal in the Microsoft Store? Having to install 30 GB of C++/UWP tooling, followed by a compilation that takes up another 20 GB of storage, seems pretty excessive just to try out the terminal.

Or at a minimum, maybe release the binaries on GitHub with a PowerShell script to install Cascadia. Then, you'd be able to do nightly/weekly builds.

Originally created by @jcoutch on GitHub (May 14, 2019). Would it be possible to release preview/Insider builds of Terminal in the Microsoft Store? Having to install 30 GB of C++/UWP tooling, followed by a compilation that takes up another 20 GB of storage, seems pretty excessive just to try out the terminal. Or at a minimum, maybe release the binaries on GitHub with a PowerShell script to install Cascadia. Then, you'd be able to do nightly/weekly builds.
claunia added the Resolution-Answered label 2026-01-30 22:15:31 +00:00
claunia commented 2026-01-30 22:15:32 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (May 14, 2019):

This is exactly what is going to happen in June, when the terminal will be in a better, more usable state. The current build of the terminal is really only intended for experienced developers, not for admins and power users (hence the proliferation of issues regarding building it!) This also helps us debug issues with building the terminal across a wide range of scenarios, environments and platforms. Publishing the current terminal to Windows Store now will undoubtedly cause an absolute torrent of issues to be logged, most of them duplicates and probably already solved by the time we get around to triaging them :) So, please be patient -- it's coming.

@oising commented on GitHub (May 14, 2019): This is exactly what is going to happen in June, when the terminal will be in a better, more usable state. The current build of the terminal is really only intended for experienced developers, not for admins and power users (hence the proliferation of issues regarding building it!) This also helps us debug issues with building the terminal across a wide range of scenarios, environments and platforms. Publishing the current terminal to Windows Store now will undoubtedly cause an absolute torrent of issues to be logged, most of them duplicates and probably already solved by the time we get around to triaging them :) So, please be patient -- it's coming.
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 Resolution-Answered
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#1059
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?