MQTTnet VS Eto.Forms

MQTT https://github.com/dotnet/MQTTnet

MQTTNet - High perf IOT comms for .NET - https://github.com/dotnet/MQTTnet

I'm trying to use MQTT.Net and so far everything works.. except for event handling.

Like the other guy said it depends on the requirements, but you could implement your own mqtt server with MQTTnet with a few lines of code

For the server we used mosquitto because we already used it in the past (and it's relatively simple), for the client MQTTnet because it's .net and it seemed good enough (mosquitto has a client library too but it's C so I'd have to write some interop). It's a simple protocol so it shouldn't really matter which implementation you use.

We are going to use MQTTNet as the foundation for this article, although the same concepts can be applied with any other MQTT client.

[2] https://github.com/dotnet/MQTTnet

For example, I used MQTTnet which is a very nice (high performance & extensible) library. And it's free/open source. If you're not writing your server code in .NET, then look for whatever broker libraries are available on your server platform.

An option that does not seem to have been mentioned yet is Eto.Forms: https://github.com/picoe/Eto

And the above is caused by https://github.com/picoe/Eto/issues/2361

Eto Forms - Simple cross-platform UI toolkit using native components, also for F# - https://github.com/picoe/Eto

Yes, you can use Eto.Forms. There is also Windows Forms (with WYSIWYG editor).

Check out Eto Forms

Look at the Wiki: Containers

To move on to GUI dev, there's the Qt Framework, Eto.forms for C#; Rust has the ImGui wrapper for the C++ Dear ImGui library.

I've been using Eto Myself