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

Why the Windows Store? #10994

New Issue
Closed
opened 2026-01-31 02:35:45 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 02:35:45 +00:00
Owner
Copy Link

Originally created by @DBJDBJ on GitHub (Oct 12, 2020).

I am perhaps looking from high-up, sorry if this was explained elsewhere. It is not clear why the involvement of the Windows Store? It this a UWP app? Is this a pure WIN32 App?

Originally created by @DBJDBJ on GitHub (Oct 12, 2020). I am perhaps looking from high-up, sorry if this was explained elsewhere. It is not clear why the involvement of the Windows Store? It this a UWP app? Is this a pure WIN32 App?
claunia commented 2026-01-31 02:35:46 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (Oct 12, 2020):

Its a hybrid app (in advance of WinUI 3.0) and the Windows Store can provide more than just UWP apps

@mdtauk commented on GitHub (Oct 12, 2020): Its a hybrid app (in advance of WinUI 3.0) and the Windows Store can provide more than just UWP apps
claunia commented 2026-01-31 02:35:46 +00:00
Author
Owner
Copy Link

@DBJDBJ commented on GitHub (Oct 12, 2020):

Thank's @mdtauk ... Although the question remains unanswered: Why the Windows Store?
And suddenly there are two more questions.

  1. Why the Windows Store?
  2. Why the Hybrid App?
  3. Why WinUI 3.0?

Three clear and simple questions in total 😉

And now one "why" into my direction: Why am I asking this? Simply because I was under the impression this (Windows Terminal) will replace Terminal host, cmd.exe and PowerShell, etc in Windows 10 with this one superior product?

@DBJDBJ commented on GitHub (Oct 12, 2020): Thank's @mdtauk ... Although the question remains unanswered: Why the Windows Store? And suddenly there are two more questions. 1. Why the Windows Store? 2. Why the Hybrid App? 3. Why WinUI 3.0? Three clear and simple questions in total :wink: And now one "why" into my direction: Why am I asking this? Simply because I was under the impression this (Windows Terminal) will replace Terminal host, cmd.exe and PowerShell, etc in Windows 10 with this one superior product?
claunia commented 2026-01-31 02:35:46 +00:00
Author
Owner
Copy Link

@PhMajerus commented on GitHub (Oct 12, 2020):

Windows Terminal will never replace cmd.exe and PowerShell because these are completely different things.
cmd.exe and PowerShell are text-based apps (aka CUI) that use text streams as their inputs and outputs instead of pixels and events, conhost and Terminal are apps that lets you interact with such apps by providing a graphical interface for them that produces the pixels and handle inputs acting as the frontend for CUI apps.

Terminal will probably replace conhost for new CUI apps, but conhost will remain for legacy support as they are not completely interchangeable for some cases.

@PhMajerus commented on GitHub (Oct 12, 2020): Windows Terminal will never replace cmd.exe and PowerShell because these are completely different things. cmd.exe and PowerShell are text-based apps (aka CUI) that use text streams as their inputs and outputs instead of pixels and events, conhost and Terminal are apps that lets you interact with such apps by providing a graphical interface for them that produces the pixels and handle inputs acting as the frontend for CUI apps. Terminal will probably replace conhost for new CUI apps, but conhost will remain for legacy support as they are not completely interchangeable for some cases.
claunia commented 2026-01-31 02:35:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 12, 2020):

  1. We're using the Windows Store because it's an effective means of deploying and distributing our application to users without the team having to do much work ourselves. It also makes delivering updates easier. We're also deploying releases on our github page.
  2. We're one of the first of a new class of applications. These "hybrid" apps aren't really Win32 apps, and they're not really UWP apps. In the near future, developers for Windows should stop treating the two as separate targets. In our case, we wanted to use UWP XAML to have a modern UI experience, but we needed some classing win32 APIs for connecting to commandline client applications. So building the terminal as a "hybrid" win32 application using XAML Islands was the only way to make this possible.
  3. WinUI 3.0 is just the next iteration on the concept of these hybrid applications. We're actually not using WinUI 3 yet (because it's still only in preview), but we are using WinUI 2.(something)

The Terminal is here to replace conhost.exe, the "window" for applications like cmd.exe and powershell. The Terminal can be used to run lots of different commandline applications, including linux shells with WSL.

@zadjii-msft commented on GitHub (Oct 12, 2020): 1. We're using the Windows Store because it's an effective means of deploying and distributing our application to users without the team having to do much work ourselves. It also makes delivering updates easier. We're also deploying releases on [our github page](https://github.com/microsoft/terminal/releases). 2. We're one of the first of a new class of applications. These "hybrid" apps aren't really Win32 apps, and they're not really UWP apps. In the near future, developers for Windows should stop treating the two as separate targets. In our case, we wanted to use UWP XAML to have a modern UI experience, but we needed some classing win32 APIs for connecting to commandline client applications. So building the terminal as a "hybrid" win32 application using XAML Islands was the only way to make this possible. 3. [WinUI](https://github.com/microsoft/microsoft-ui-xaml/) 3.0 is just the next iteration on the concept of these hybrid applications. We're actually not using WinUI 3 yet (because it's still only in preview), but we are using WinUI 2.(something) The Terminal is here to replace `conhost.exe`, the "window" for applications like `cmd.exe` and `powershell`. The Terminal can be used to run lots of different commandline applications, including linux shells with [WSL](https://github.com/microsoft/WSL/).
claunia commented 2026-01-31 02:35:47 +00:00
Author
Owner
Copy Link

@DBJDBJ commented on GitHub (Oct 13, 2020):

@zadjii-msft Many thanks Mike. Is there any info somewhere how can we make Visual Studio projects that will target The Terminal instead of cmd.exe? I assume this is one of those too obvious to see. Thanks ...

@DBJDBJ commented on GitHub (Oct 13, 2020): @zadjii-msft Many thanks Mike. Is there any info somewhere how can we make Visual Studio projects that will target The Terminal instead of cmd.exe? I assume this is one of those too obvious to see. Thanks ...
claunia commented 2026-01-31 02:35:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 13, 2020):

Not currently. The long-term plan is to allow users to set a "default terminal" application on Windows, so that all console applications will spawn the specified terminal, rather than conhost.exe (the vintage console window). That work's being tracked over in #492

@zadjii-msft commented on GitHub (Oct 13, 2020): Not currently. The long-term plan is to allow users to set a "default terminal" application on Windows, so that all console applications will spawn the specified terminal, rather than `conhost.exe` (the vintage console window). That work's being tracked over in #492
claunia commented 2026-01-31 02:35:47 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 17, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Oct 17, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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 Issue-Question Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity 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#10994
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?