Caliburn.Micro icon indicating copy to clipboard operation
Caliburn.Micro copied to clipboard

Published 20 hours ago • verified publisher icon Caliburn-Micro

RFC: Do somebody work on WinUI 3 support?

Open glyad opened this issue 2 years ago • 11 comments

Since WinUI 3 support was announced before a year, as I remember, I tried to find any work done. It seems like no one is working on it.

glyad avatar Aug 23 '22 11:08 glyad

I think @vb2ae is working on it, I might pick up the torch as I have just finished the MAUI implementation.

KasperSK avatar Aug 23 '22 11:08 KasperSK

@vb2ae, maybe I wrong, I searched both in the original repo and in your fork as well, but I haven't found a branch related to work on support of WinUI 3.

It's really important me to know, if somebody works on it and what/when to expect regarding that.

Thank you for attention to my questions

glyad avatar Aug 23 '22 11:08 glyad

@glyad I am not sure if we have any time line for it. What are your needs?

KasperSK avatar Aug 23 '22 12:08 KasperSK

@glyad I can look at it this weekend. still have a few bugs to work out

vb2ae avatar Aug 23 '22 16:08 vb2ae

@vb2ae of you make a WIP pull request I would be happy to pitch in.

KasperSK avatar Aug 23 '22 16:08 KasperSK

I will working on merging the maui branch in with it tonight and make a wip pull request

vb2ae avatar Aug 23 '22 16:08 vb2ae

@glyad I am not sure if we have any time line for it. What are your needs?

I have an order for the development windows desktop application. My client wants it developed using WinUI 3. Currently I'm trying to convince the client to use the WPF to prevent unpredictable troubles with WinUI 3 and because of the absence of infrastructures. Anyway,.. if my client continues to require WinUI, I will need to develop it with WinUI. So,.. I need to know, if somebody works on WinUI 3 version of CM.

BTW, I'm one of contributors of LogoFX/MVVM. Currently we support only WPF. In previous versions we supported Silverlight, WinRT, WinPhone, UWP, Xamarin, but now we don't support it, because of absence of interest to those technologies from our clients. If somebody helps to build WinUI 3 version of CM and if we're still needing to develop the app mentioned above using WinUI 3, I will work on platform dependent version of LogoFX/MVVM.

@KasperSK and @vb2ae, Thank you a lot for your attention to community demands! We appreciate your work, because we (LogoUI) built more than 150 serious solutions based XAML-enabled frameworks, mainly WPF and Silverlight, for our clients using Caliburn.Micro and LogoFX (https://github.com/LogoFX/Samples.Specifications).

glyad avatar Aug 25 '22 14:08 glyad

@glyad I can look at it this weekend. still have a few bugs to work out

Hi @vb2ae,

Have you looked to WinUI 3 branch? Do you have some update? Also, I would be appreciated, if you could point me to WinUI 3 development branch.

Thank you in advance

glyad avatar Sep 11 '22 13:09 glyad

I am still having some issues. It is having a problem resolving the views when I use the navigation service. https://github.com/Caliburn-Micro/Caliburn.Micro/tree/winappsdk is the branch I am in working in

vb2ae avatar Sep 13 '22 00:09 vb2ae

Thank you very much for the update @vb2ae,

I'll try to look on this later. Is it only the issue that you're talked about?

Have you an estimations or plans, when the version supporting WinUI 3 will be published?

glyad avatar Sep 13 '22 09:09 glyad

That is the only issue I know of now. Plan to create a winappsdk version of the features app to make sure everything is working

vb2ae avatar Sep 13 '22 12:09 vb2ae