The PInvoke code in this .NET library is hand-crafted by developer Paul Knopf to ensure appropriate memory management and pointer ownership semantics. He is pretty confident about the library and mentions in his blog “I’d bet you couldn’t generate a segfault, even if you wanted to.”
This has an added benefit of keeping your business/UI concerns separate cleanly. There will also be no chatty PInvoke calls for rendering. It is a great match.
Qml.Net support and working
Qml.Net will work with any .NET language including popular C# and functional languages like F#. Your libraries will reference the pure .NET NuGet package, Qml.Net. The host process (Program.Main) references the native NuGet packages. This is dependent on the OS you are on:
Qml.Net.WindowsBinaries Qml.Net.OSXBinaries Qml.Net.LinuxBinaries
Paul currently only tests his own models that are C# objects registered with the QML engine. They are specific to each control/page.
Since Microsoft’s announcement of .NET Core, there hasn’t been any clear idea on cross-platform GUI development. Although Microsoft plans to support WPF in .NET Core 3.0, it will be limited to Windows machines.
With community involvement and support, Qml.net can be a potential game changer. You can head to the GitHub repository and also view some hosted examples to get a better idea.
Exciting New Features in C# 8.0
.NET Core completes move to the new compiler – RyuJIT
Microsoft Azure’s new governance DApp: An enterprise blockchain without mining