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

WinUI3 : Would it be a technical solution to ship Windows Terminal outside the store ? #12754

New Issue
Closed
opened 2026-01-31 03:23:58 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:23:58 +00:00
Owner
Copy Link

Originally created by @tebeco on GitHub (Feb 26, 2021).

Description of the new feature/enhancement

As WinUI 3 is supposed to

  • be able to ship application to older version of windows and still keeping compatibility with new feature
  • Enhance current UWP state
    and few other thing. That would be the perfect opportunity to use that to remove the infamous bug of

"If the Store is locked, you won't ever be able to run WT be double clicking msixbundle and this will also

  • Not be needed to manually rename
  • Manually unzip
  • Manually renamed what was in the zip to ... another zip
  • Manually unzip again
  • Update the Path
  • Can't be used as a $PROFILE script because WT cannot update itself

Would that be a more ideal way to ship to company ? (which mostly have the store lockdown)

Originally created by @tebeco on GitHub (Feb 26, 2021). # Description of the new feature/enhancement As WinUI 3 is supposed to * be able to ship application to older version of windows and still keeping compatibility with new feature * Enhance current UWP state and few other thing. That would be the perfect opportunity to use that to remove the infamous bug of "If the Store is locked, you won't ever be able to run WT be double clicking `msixbundle` and this will also * Not be needed to manually rename * Manually unzip * Manually renamed what was in the zip to ... another zip * Manually unzip again * Update the Path * Can't be used as a $PROFILE script because WT cannot update itself Would that be a more ideal way to ship to company ? (which mostly have the store lockdown)
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 03:23:59 +00:00
claunia commented 2026-01-31 03:23:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 26, 2021):

Maybe, but I'd doubt it. I think WinUI 3 is supposed to help blur the lines between Win32 and UWP, so that we can have a more UWP-like experience, and don't need to do all the XAML islands tricks we're currently doing. I don't think that there's anything about WinUI 3 that's really going to change how packaged applications work, however.

@zadjii-msft commented on GitHub (Feb 26, 2021): Maybe, but I'd doubt it. I think WinUI 3 is supposed to help blur the lines between Win32 and UWP, so that we can have a more UWP-like experience, and don't need to do all the XAML islands tricks we're currently doing. I **don't** think that there's anything about WinUI 3 that's really going to change how packaged applications work, however.
claunia commented 2026-01-31 03:24:00 +00:00
Author
Owner
Copy Link

@tebeco commented on GitHub (Feb 26, 2021):

Could it be coupled with click once or equivalent then ?
I mean literally any other way to ship than the store if WinUi3 allow to get back compat to newer OS feature in older one

@tebeco commented on GitHub (Feb 26, 2021): Could it be coupled with click once or equivalent then ? I mean literally any other way to ship than the store if WinUi3 allow to get back compat to newer OS feature in older one
claunia commented 2026-01-31 03:24:00 +00:00
Author
Owner
Copy Link

@huoyaoyuan commented on GitHub (Mar 9, 2021):

I wonder why msix double clicking is disabled when the store is disabled. Msix is meant to act more than store. It can contain win32 applications.

@huoyaoyuan commented on GitHub (Mar 9, 2021): I wonder why msix double clicking is disabled when the store is disabled. Msix is meant to act more than store. It can contain win32 applications.
claunia commented 2026-01-31 03:24:00 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 10, 2021):

As far as we are aware, double-clicking an MSIX has nothing to do with the store.

Mike answered this very well -- I'm gonna close it out as an answered question. We're not in a place where we can benefit from WinUI3 today.

@DHowett commented on GitHub (Mar 10, 2021): As far as we are aware, double-clicking an MSIX has nothing to do with the store. Mike answered this very well -- I'm gonna close it out as an answered question. We're not in a place where we can benefit from WinUI3 today.
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-Tag-Fix 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#12754
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?