Xamarin.Forms VS WPF

EDIT2: Yeah, https://github.com/xamarin/Xamarin.Forms/issues/2751

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?

The deploying is also very buggy in my project, see this post: https://github.com/xamarin/Xamarin.Forms/issues/15253

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.

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.

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

BTW this is the reported issue, please comment to push xamarin team look over it and maybe fix the bug

I'm worried that I'm experiencing this unresolved issue on GitHub.

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

Gear up, folks, and test drive this fresh-off-the-lab feature. And should you stumble upon any glitches along the way, don’t hesitate to reach out. Got a bug to report or feedback to give? Send them directly to our dotnet/wpf repository. We’re eager to hear from you, because together, we’re only going to make the experience even better!

I did some research and did not find any proof of the EOL on WPF. In fact, Microsoft just updated the roadmap on WPF 2 months ago.

There’s still room for improvement though. I should add, WPF on .NET Core consumes a lot of memory, due to a memory leak. It was logged by our COO as one of our users was doing a comparison.

have you tried this?

WPF: Licencia MIT.

Some added context: It's a side effect of how variable rendering works in UI library we use. There's currently sadly no way how to disable VRR compatibility, which causes the issue you describe unless you tell your GPU to not treat Playnite as VRR compatible. Some more info here.

WPF is definitely not dead. It may not be the latest shiny thing, but it works, it is maintained (judging by https://github.com/dotnet/wpf or https://devblogs.microsoft.com/dotnet/wpf-on-dotnet-7/), and it is fully and officially supported on the modern .NET platform.

This article only sights a video stream. I think part of the problem with the glacial pace of development is reliance on manual testing. See this comment:

https://github.com/dotnet/wpf/discussions/7130#discussioncom...

> Our primary goal is to ensure reduced turn-around-times for new PRs as well as clear the pending backlog of existing PRs. To that end, we are working on putting appropriate automation in place to reduce the dependency on manual testing as much as we can.

See also the recently updated WPF roadmap:

https://github.com/dotnet/wpf/blob/main/roadmap.md

If you look at the history of this file you can over the years tests have been always been in the backlog.

As for “where projects go to die”, they have 3 features planned for this year: Windows 11 Theming, a new type of folder browser, and null ability annotations. And they say they don’t think they can do them all. Maybe I’m underestimating, but that’s not a lot.