Terminal: make Windows Terminal available to v1809

Created on 26 Jun 2019  路  13Comments  路  Source: microsoft/terminal

Summary of the new feature/enhancement

There are a significant quantity of corporate machines not able to run 1903 today for a variety of reasons (policy, compatibility, etc) and hence are locked out of terminal. I wasn't able to find much discussion about the reasons that exist for 1903 to be a requisite.
image

Area-Build Issue-Question Product-Terminal Resolution-Answered

Most helpful comment

Sorry. Right now, there's two big blockers to adoption on 1809.

  • XAML islands was a technology preview and didn't support high-DPI, DPI changes, or accessibility in 1809. We rely on them heavily.
  • 1903 added support for side-by-side WinRT component activation, something deep in the COM stack that lets us find our DLLs when they're right next to our EXE.

We just can't go back to 1809.

All 13 comments

In my guessing, there is probably a feature within the windows source code that is used in the new terminal which is why 1903 is required.

I guess it's because maintaining compatibility is a trouble. You CAN try to run on 1809 but without any support.

Sorry. Right now, there's two big blockers to adoption on 1809.

  • XAML islands was a technology preview and didn't support high-DPI, DPI changes, or accessibility in 1809. We rely on them heavily.
  • 1903 added support for side-by-side WinRT component activation, something deep in the COM stack that lets us find our DLLs when they're right next to our EXE.

We just can't go back to 1809.

We just can't go back to 1809.

TY for the detail

We just can't go back to 1809.

Please Microsoft, fix the Surface Book 2 then so we can upgrade! 馃槶

It looks like WInUI 3.0 will backport full XAML Islands support to most versions of Windows 10 and is releasing this year - could you use WinUI 3.0 to add support for Windows Terminal on earlier versions of Windows 10?

That's certainly a possibility we'd have to investigate. If XAML Islands was detached from the platform, then I'm not sure how many of our own features are actually dependent upon 1903.

I guess Dustin mentioned the SxS winrt activation above - I'm not _positive_ that is still needed, but if it is, then that might be exceptionally hard for us to overcome. That would be one of the things to investigate when WinUI 3.0 is available.

WinUI 3.0

It seems to me that there is now a preview available for it: https://docs.microsoft.com/en-us/windows/apps/winui/winui3/

XAML Islands is not supported in this release

That's the single most important part of the WinUI stack we need, so unfortunately, that's a non-starter for us. Don't worry, we work pretty closely with the WinUI team (in the same hallway in fact), so when WinUI 3 is ready for us to move to it, we'll work on it 馃槈

WinUI 3.0 Preview 2 has been released some days ago. Anything new on LTSC support?

https://docs.microsoft.com/en-us/windows/apps/winui/winui3/

Seems to still quote "XAML Islands is not supported in this release" on the preview 2 release notes.

I've gone ahead and marked up their list of limitations with ones that stop us from being able to use Preview 2:
image

image

As I've said before, we won't be able to start experimenting with WinUI 3.0 until there's support for XAML Islands.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

wkbrd picture wkbrd  路  3Comments

miniksa picture miniksa  路  3Comments

DieselMeister picture DieselMeister  路  3Comments

alabuzhev picture alabuzhev  路  3Comments

carlos-zamora picture carlos-zamora  路  3Comments