make Windows Terminal available to v1809 #2277

@JushBJJ commented on GitHub (Jun 26, 2019):

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.

@JushBJJ commented on GitHub (Jun 26, 2019): 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.

claunia commented

@ysc3839 commented on GitHub (Jun 26, 2019):

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

@ysc3839 commented on GitHub (Jun 26, 2019): I guess it's because maintaining compatibility is a trouble. You CAN try to run on 1809 but without any support.

claunia commented

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

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.

@DHowett-MSFT commented on GitHub (Jun 26, 2019): 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.

claunia commented

@fredless commented on GitHub (Jun 26, 2019):

We just can't go back to 1809.

TY for the detail

@fredless commented on GitHub (Jun 26, 2019): > We just can't go back to 1809. TY for the detail

claunia commented

@brunofin commented on GitHub (Sep 11, 2019):

We just can't go back to 1809.

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

@brunofin commented on GitHub (Sep 11, 2019): > We just can't go back to 1809. Please Microsoft, fix the Surface Book 2 then so we can upgrade! 😭

claunia commented

@NetMage commented on GitHub (Mar 12, 2020):

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?

@NetMage commented on GitHub (Mar 12, 2020): 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?

claunia commented

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

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.

@zadjii-msft commented on GitHub (Mar 12, 2020): 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.

claunia commented

@superm1 commented on GitHub (Jun 23, 2020):

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/

@superm1 commented on GitHub (Jun 23, 2020): > 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/

claunia commented

@zadjii-msft commented on GitHub (Jun 23, 2020):

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 😉

@zadjii-msft commented on GitHub (Jun 23, 2020): > 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 😉

claunia commented

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

@sidietz commented on GitHub (Jul 17, 2020):

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

@sidietz commented on GitHub (Jul 17, 2020): 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/

claunia commented

@superm1 commented on GitHub (Jul 17, 2020):

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

@superm1 commented on GitHub (Jul 17, 2020): Seems to still quote "XAML Islands is not supported in this release" on the preview 2 release notes.

claunia commented

@DHowett commented on GitHub (Jul 17, 2020):

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

@DHowett commented on GitHub (Jul 17, 2020): I've gone ahead and marked up their list of limitations with ones that stop us from being able to use Preview 2: ![image](https://user-images.githubusercontent.com/189190/87824055-6a3fc580-c829-11ea-8ca7-8d18cc0e9ec3.png)

claunia commented

@zadjii-msft commented on GitHub (Jul 17, 2020):

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

@zadjii-msft commented on GitHub (Jul 17, 2020): ![image](https://user-images.githubusercontent.com/18356694/87823948-fe198d80-c839-11ea-818d-4b4cf5d7fecf.png) As I've said before, we won't be able to start experimenting with WinUI 3.0 until there's support for XAML Islands.

claunia commented

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

Can we migrate the whole app to WinUI on Desktop instead of a Win32 Window with XAML islands?

@driver1998 commented on GitHub (Mar 9, 2021): Can we migrate the whole app to WinUI on Desktop instead of a Win32 Window with XAML islands?

claunia commented

@zadjii-msft commented on GitHub (Mar 9, 2021):

@driver1998 At some point sure.

Last I checked (and this was a while ago), it would still be a while before WinUI3 supported custom content in the titlebar, and host backdrop acrylic. We fairly aggressively customize our own titlebar, and a lot of users really like acrylic and would be sad to see it go.

Now, that was a while ago, and priorities might have changed since then. So those features might be supported in the official first WinUI 3 release.

We've also got to balance the needs of our own engineering efforts. Moving to WinUI 3 would probably mean a whole month for a dev of just porting code and making sure nothing breaks. That's a month that we can't use on any of the other things that we've already committed to for Terminal v2. The WinUI 3 project layout is far nicer and will probably be better in the long run, but right now the Terminal's .sln is a bit of a house of cards. It's got a bunch of carefully constructed hacks in it to make sure the Terminal builds just right. Making sure those hacks still work in WinUI 3 is what would take the majority of the time.

WinUI 3 is probably one of the higher Terminal v3 priorities, it's just not in the cards for v2. We'd rather stick with the devil we know for now.

@zadjii-msft commented on GitHub (Mar 9, 2021): @driver1998 At some point sure. Last I checked (and this was a while ago), it would still be a while before WinUI3 supported custom content in the titlebar, and host backdrop acrylic. We fairly aggressively customize our own titlebar, and a lot of users really like acrylic and would be sad to see it go. Now, that was a while ago, and priorities might have changed since then. So those features might be supported in the official first WinUI 3 release. We've also got to balance the needs of our own engineering efforts. Moving to WinUI 3 would probably mean a whole month for a dev of just porting code and making sure nothing breaks. That's a month that we can't use on any of the other things that we've already committed to for Terminal v2. The WinUI 3 project layout is _far_ nicer and will probably be better in the long run, but right now the Terminal's `.sln` is a bit of a house of cards. It's got a bunch of carefully constructed hacks in it to make sure the Terminal builds _just right_. Making sure those hacks still work in WinUI 3 is what would take the majority of the time. WinUI 3 is probably one of the higher Terminal v3 priorities, it's just not in the cards for v2. We'd rather stick with the devil we know for now.

claunia commented

@sidietz commented on GitHub (Jun 10, 2021):

After another three months having passed:
Is there any update on the WinUI3 transition?

@sidietz commented on GitHub (Jun 10, 2021): After another three months having passed: Is there any update on the WinUI3 transition?

claunia commented

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

No, and it is neither in our roadmap nor committed or planned to ever happen. 😄

@DHowett commented on GitHub (Jun 10, 2021): No, and it is neither in our roadmap nor committed or planned to ever happen. :smile:

claunia commented