pinvoke VS Avalonia

Hooks are a low-level Win 32 API and are not directly exposed from the BCL, so you either need to write your own P/Invoke code (maybe using something like https://github.com/dotnet/pinvoke)

To add to the pile of solutions for this: https://github.com/dotnet/pinvoke

I'm using the PInvoke libraries (cf. https://github.com/dotnet/pinvoke/). And if my mouse hovers a split of a second over PInvoke.User32 or even worse PInvoke.Kernel32, VS will freeze for 2 minutes trying to render the very big summary of those classes.

> I don't see any other way to go trully multi platform without making separate UI for Android and iOS.

https://avaloniaui.net/

My understanding is that most of the new generation of GUI frameworks/application runtime are targeting all platforms. And there's clearly a demand for such feature set if the popularity of Electron says anything. Software businesses no longer want to specialize on specific platforms. What's more, it's provably[0] doable[1] to[2] do[3] so[4]. So, why shouldn't they?

    [0]: https://avaloniaui.net/

6- avalonia

Avalonia has always been a labour of love, a community-driven project open to all. Over the past decade, more than 300 contributors worldwide have shaped Avalonia into what it is today. Avalonia v11 is not just a new version; it embodies our vibrant community's collective hard work and ambition to create the best cross-platform UI framework.

I was going to ask if you had considered Avalonia for UI but it looks like you're using third party controls that might make porting difficult. The primary advantage would be Linux and Mac compatibility but it looks like quite a job.

Look at AvaloniaUI, it’s .NET and basically an open source, cross platform WPF: https://avaloniaui.net/

I'll counter with Avalonia https://avaloniaui.net/

It's likely easier if you assume the same starting skill level since dotnet build system is way simpler to deal with.