Xamarin.Forms
Windows UI Library
Xamarin.Forms | Windows UI Library | |
---|---|---|
27 | 102 | |
5,637 | 6,037 | |
- | 0.9% | |
6.1 | 7.7 | |
6 days ago | 4 days ago | |
C# | C++ | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Xamarin.Forms
-
How To Update Picker To Property Value On Load
EDIT2: Yeah, https://github.com/xamarin/Xamarin.Forms/issues/2751
-
What are some of Xamarin Forms shortcomings/cons which Maui still doesn't address?
Example issue: https://github.com/xamarin/Xamarin.Forms/issues/8640 Its an issue reported by David O, its a 3 year old issue, there is limited communication from Microsoft on the issue, no plans, there are a couple of community discovered workarounds that got broken in later versions of Xamarin.Forms. I feel like its fairly common to come across an issue like this that can be a showstopper for a task. Do you come up with a workaround, do you wait for an official fix, do you use a third-party NuGet to accomplish the task?
- Is it possible to change text colour in the pop up generated by a date picker in Android?
-
Have teams that migrated to Visual Studio 2022 with their Xamarin Forms app experienced a smooth transition?
The deploying is also very buggy in my project, see this post: https://github.com/xamarin/Xamarin.Forms/issues/15253
-
Overwhelmed by different technolgies for projects in C#, are there any resources of various projects I can follow?
Xamarin, it is "cross-platform" in the sense that it makes cross-platform applications, for Android and IOS and Windows. There are some implementations of Xamarin for other platforms like Linux (GTK#) or MacOs, but they're not really mature and stable yet. See https://github.com/xamarin/Xamarin.Forms/wiki/Platform-Support for more details.
-
collectionview scroll to mvvm
It appears there is no view binding for this function... I've been googling around and saw this post https://github.com/xamarin/Xamarin.Forms/issues/10254 , but I can't implement it properly. It fails out with a dictionary exception.
-
Legacy Xamarin Native App, stick with Xamarin Native or change to Xamarin Forms / Maui?
You asked a bunch of questions there, I will try to answer them separately. 1) I am a XN expert and have a ton of experience in it, and from my research, it’s extremely difficult to get an experienced xamarin native developer. Xamarin Native is amazing experience to have, but There’s literally NO WAY left for someone to train themselves in xamarin native and I wrote about that here https://blog.devgenius.io/usingxamarinuniversitytolearnmobiledevelopment-808b6dec3e8b?sk=1c196f32400196f14dff7359f8ee51c0 So yes, I highly recommend running away from using xamarin native apps. Companies are having such a hard time finding experienced devs at regular rates. So anything is better really. 2) As to what language to select, Cross Platform >> Swift/Kotlin, these are also specialized skills that are just as rare to find both of in one senior skilled developer. Microsoft is actually putting in a lot of effort into building out the new Maui platform which is a piece of cake for xamarin forms developers to learn. There’s several migration tools already built as well, and the advantage of using Xamarin for you would be that you can keep your ViewModel layer exactly the same, you just have to build your view layer (also pretty easy to do with hot reload). Finally, it is important to note that more than 50% of ALL new mobile app development is moving towards React Native. The ability to use typescript (TS) instead of JavaScript removed the biggest negative against RN. Also keep in mind there’s no easy way of migrating from Xamarin Native to Xamarin forms except for starting a Xamarin forms app from scratch because of This issue https://github.com/xamarin/Xamarin.Forms/issues/8153
-
Stacklayout cutting off some content on Android
BTW this is the reported issue, please comment to push xamarin team look over it and maybe fix the bug
-
Shell App Navigation Error on Android: "Ambiguous routes matched"
I'm worried that I'm experiencing this unresolved issue on GitHub.
-
Miliseconds of irresponsiveness when Xamarin opens a view for first time. Is this a Xamarin thing?
If you're using shell on Android, this is a prevelant problem as your binding count grows. There has been a bug open on the Xamarin team for two years that keeps getting pushed in favor of MAUI work. https://github.com/xamarin/Xamarin.Forms/issues/7521
Windows UI Library
- WinUI 3 is now open source
- WinUI3 Source Available
- Can't publish WinUI 3 app
- Leaked Microsoft poll shows fewer employees have confidence in leadership
- Should I start migrating my Xamarin app to MAUI
-
When are we going to have smooth animations ?
I wish that was true, but even the new stuff, like their new frameworks, performs poorly while their older frameworks perform really well. That's brand new code, with no legacy codebase to care for.
-
WinUI Unpackaged --- What am I missing?
The reason why I don't recommend Winui is the million bugs it has. See the github issues page. All Microsoft ui stuff sucks currently. But if you use WPF why not FluentWPF
- Visual Studio UI will get redesigned
-
For the past year and a half I've been working on Wintoys, an app that let's you experience Windows in your way and keep it fresh everyday while having everything you need in one place
Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.
-
Build 23451 includes a better implementation of improved File Explorer tab dragging (you can drag tabs out to create a new window or drag between windows) - still a bit buggy but nice to see anyway!
Compared to UWP or WPF, WinUI 3 is somewhere between 100-200% slower and consumes 7-20 times as much RAM as the old frameworks (for certain operations).
What are some alternatives?
Avalonia - Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The most popular .NET UI client technology
MahApps.Metro - A framework that allows developers to cobble together a better UI for their own WPF applications with minimal effort.
Gtk# - Gtk# is a Mono/.NET binding to the cross platform Gtk+ GUI toolkit and the foundation of most GUI apps built with Mono
SecureUxTheme - 🎨 A secure boot compatible in-memory UxTheme patcher
Eto.Forms - Cross platform GUI framework for desktop and mobile applications in .NET
WPF - WPF is a .NET Core UI framework for building Windows desktop applications.
Fluent.Ribbon - WPF Ribbon control like in Office
metroframework-modern-ui - My humble attempt to bring the new Modern UI alias Metro UI of Windows 8 to .NET Windows Forms applications.
FlatLaf - FlatLaf - Swing Look and Feel (with Darcula/IntelliJ themes support)