hivemq-mqtt-client-dotnet
hivemq-mqtt-client-dotnet copied to clipboard
hivemq
FR: Add legacy support for .Net Framework 4.7.2
Is this library compatible with .Net Framework 4.7.2? i was able to use it with .Net Core 6 , worked flawlessly but facing issues with .Net Framework, or is there any workaround?
Hello @amitsahu-work, thanks for contributing to the HiveMQ community! We will respond as soon as possible.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @amitsahu-work - Unfortunately not. This library was built against .NET 6.0 which implements .NET Standard 2.1 (see here). And .NET Framework doesn't support this latest standard (see here).
Hi @amitsahu-work - Unfortunately not. This library was built against .NET 6.0 which implements .NET Standard 2.1 (see here). And .NET Framework doesn't support this latest standard (see here).
hey @pglombardo can you suggest a mqtt client library for .Net Framework 4.7.2 which supports persistence of messages while disconnected
"persistence of messages while disconnected"
This could mean a couple thing but I don't know of any C# client that has local file persistence. I'd like to add that to this client eventually but there is no ETA currently.
Also note that the HiveMQ broker will queue Quality of Service level 1 and 2 messages when the client goes offline. Once you reconnect (with CleanStart=false) all of the queued messages will be delivered upon reconnecting.
See the ConnectReceiveAndPublish example that offers a bit more explanation and code.
The queue size and discard strategy can be configured in the HiveMQ broker. See the documentation here.
"persistence of messages while disconnected"
This could mean a couple thing but I don't know of any C# client that has local file persistence. I'd like to add that to this client eventually but there is no ETA currently.
Also note that the HiveMQ broker will queue Quality of Service level 1 and 2 messages when the client goes offline. Once you reconnect (with
CleanStart=false) all of the queued messages will be delivered upon reconnecting.See the ConnectReceiveAndPublish example that offers a bit more explanation and code.
The queue size and discard strategy can be configured in the HiveMQ broker. See the documentation here.
Thanks @pglombardo i have explored that option , it seems HiveMQ .net library does not support .net framework 4.7.2, if you have anything else in mind would appreciate
Hi @amitsahu-work if you have a HiveMQ broker license, contact your sales rep and have the request communicated. Possibly we can get in a FR to add legacy support.