themesof.net VS MQTTnet

This is a good one, though it's more vague then a typical roadmap https://themesof.net/

Right, so, if we're going to talk about unreleased, future features, then I have a little roadmap here to show you.

The dotnet team at least does use it in a number of stuff. Tye's dashboard UI uses Blazor server, and if I recall some parts of MS docs uses Blazor WASM to evaluate C# code in the browser. dotnet live and https://themesof.net/ uses Blazor server as well.

Having said that, charting is a very basic and fundamental enterprise application requirement, so we do support that. As a matter of fact we have an entire project theme (inspired from https://themesof.net/) dedicated to enterprise solution requirements, including lot of stuff from async queue-based or batch processing to allowing the end user to define their own queries and exporting results to excel and the like.

What you call "meme", I call .NET appeals to net-new developers, students, and new technologists, which is one of the Themes of .NET, which guide the platform, languages, and tooling roadmap.

There’s more information on the plans, changes, and challenges encountered with the current .NET 6 development on Microsoft’s Themes of .NET.

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.