Migration to release verison of Avalonia 11 #263
Replies: 1 comment 3 replies
-
Hello, @the-black-wolf Currently we support 11 Avalonia, but not all features are implemented yet. Currently you definitely need to use pre-releases, because it just has the most recent code with the latest fixes, etc. It's called pre-releases because we are still fixing and improving our library, but I don't think, we will introduce any major breaking changes, etc. So, you should definitely use the pre-releases for Avalonia 11 for now. As for the 3.0 release, I can't say something, but we will release asap as we support all default Avalonia controls. But I (and other maintainers) don't have a lot of time to develop for now, but I am trying to resolve issues and implement everything we need. If you are missing something, you can raise issues, and I'll try to prioritize it. DatePicker is the first thing I plan to fix. |
Beta Was this translation helpful? Give feedback.
-
Hi all,
We are in the process of planning our conversion of WPF LOBs into AvaloniaUI. We decided to focus on Avalonai 11, now that is fully released. One thing about our WPF apps is that majority of them use Material.Wpf. hence, we imagine that migrating to Material.Avalonia would play out the best. I see there was a lot of work done on 3.0_major_update branch, relating to avalonia 11, so I imagine you are already close to it.
So, a few points:
Beta Was this translation helpful? Give feedback.
All reactions