MQTTnet
Refit
MQTTnet | Refit | |
---|---|---|
13 | 33 | |
4,200 | 8,090 | |
0.8% | 1.1% | |
8.0 | 8.2 | |
8 days ago | 9 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MQTTnet
-
Communicating between 2 servers without webservice?
MQTT https://github.com/dotnet/MQTTnet
-
What your hidden nuget gems ?
MQTTNet - High perf IOT comms for .NET - https://github.com/dotnet/MQTTnet
-
Workaround for Register-ObjectEvent : Events that require a return value are not supported. ?
I'm trying to use MQTT.Net and so far everything works.. except for event handling.
-
Best way to architecture an application for IoT and RFID
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
-
Discussion Thread
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.
- Is there a library or code example on how to decode MQTT Message payload?
-
Demystifying Azure IoT Hub Device SDKs
We are going to use MQTTNet as the foundation for this article, although the same concepts can be applied with any other MQTT client.
-
Coming to .Net core from Python and Linux with what I think is a really simple project - are there any good guides to help me translate my existing knowledge?
[2] https://github.com/dotnet/MQTTnet
- 6 .NET Myths Dispelled — Celebrating (Almost) 21 Years of .NET
-
ESP32 MQTT with Firebase
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.
Refit
-
Exception Handling in C# Methods returning object
A lot of people have given you good replies, but have you looked at Refit?
-
Http calls on mobile, what is the preferred way / best practice
Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?
-
Refactor your dotNET HTTP Clients to Typed HTTP Clients
Define a Refit client interface with the following for each API endpoint, e.g. GET /foo:
-
HttpClient best approach
Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.
-
What your hidden nuget gems ?
Refit - simple, typed REST clients: https://github.com/reactiveui/refit
-
how to structure code for rest api calls
I'd advise using this https://github.com/reactiveui/refit tool for HTTP requests. It saves a lot of time for serialization, deserialization and exception handling.
-
Roadmap for transition from Java
Use Refit, and let manage the live of HttpClient. Also, Refit will give you a strongly typed client around an API. All you have to write is the interface. Ain't that neat ? If you can't, use the HttpClientFactory to create the HttpClient instance: https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests
-
ASP.NET Core - how to properly make a GET request?
Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.
-
Integration tests without API dependencies with ASP.NET Core and WireMock.Net
The controller is simple and use the Refit library to abstract the PokéAPI call and then, returns the data.
-
I love refit
To be fair, Refit is pretty great.
What are some alternatives?
SparkplugNet - SparkplugNet is a library to use the Sparkplug industrial IoT (IIoT) standard in .Net. It uses MQTTnet in the background.
RestSharp - Simple REST and HTTP API Client for .NET
Mqtt2Mqtt - Customize MQTT messages between two brokers
Flurl.Http - Fluent URL builder and testable HTTP client for .NET
SignalR-Client-Cpp - C++ Client for ASP.NET Core SignalR
RestEase - Easy-to-use typesafe REST API client library for .NET Standard 1.1 and .NET Framework 4.5 and higher, which is simple and customisable. Inspired by Refit
SignalR-Client-Cpp - C++ client for ASP.NET SignalR 2.x
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
hivemq-community-edition - HiveMQ CE is a Java-based open source MQTT broker that fully supports MQTT 3.x and MQTT 5. It is the foundation of the HiveMQ Enterprise Connectivity and Messaging Platform
Simple.OData.Client
serilog-sinks-console - Write log events to System.Console as text or JSON, with ANSI theme support
Ocelot - .NET API Gateway