.Net CF
The development of this project began in April of this year with the objective of filling the absence of a good MQTT client for all .Net platforms. After 6 months I did not expect an interest so strong against him, probably due to the wave of the Internet of Things that is coming (or is already among us ? ) . Many people are using the library for projects of varying complexity , they send me mails ( with reports but also with compliments ) and open the "issue" on the CodePlex site , which I promptly resolve . This can push me to get better and better the quality of the project , now arrived at version 2.3.0 with some bug fixes but also with an interesting new feature : all the events raised by the MqttClient class ( published message , the received message , ...) are executed in a separate thread , so the user no longer has to worry about launch "long" processing in his event handler through a new thread. With this update, I hope to have made further improvements of great interest for those who ...
Read the rest of entry »
I made a bug fix on my Library M2Mqtt (MQTT client) that allows you to better manage the case where the client does not transmit anything for a time equal to the "keep alive period " and the keep alive thread, whose task is to ping the broker to keep the connection alive, does not receive anything within the timeout period (ex. broker shutdown, network disconnection, ...).
The update is already available on CodePlex and Nuget !
After releasing the new version of my M2Mqtt library with support for SSL / TLS with server-side authentication, the time has come to show you an example of use. Choose and install the broker: Mosquitto First we have to choose an MQTT broker among those available but unfortunately no one is developed using the .Net Framework . Discarding more complex solutions , especially with regard to the installation and configuration , such as IBM Websphere , we can take into account to brokers like RabbitMQ , HiveMQ or Mosquitto. In this case , my choice was Mosquitto that we can download from the official web site for various operating systems based on Linux , as well as there is a convenient installer for the Windows environment . In fact, for Windows there are two installation modes: the first uses an installer in which the broker is compiled natively while in the second case is based on the Cygwin provides a Linux-like environment for Windows. It 'obvious that the first mode is the most simple and immediate . Afte ...
I just updated only on CodePlex (for now) M2Mqtt library (version 2.1.0.0), adding the automatic detection of any IPv6 address to connect. To determine the address class (AddressFamily), I implemented the '"Extension Method" GetAddressFamily() for the IPAddress class through the static class IPAddressUtility, necessary only because the. NET Micro Framework does not itself provide the property AddressFamily the IPAddress class. In fact, in the case of full / compact. Net Framework is returned that property while in the case of. NET Micro Framework is done by a simple search of the ":" character (separator in IPv6 addresses). 1: public static AddressFamily GetAddressFamily(this IPAddress ipAddress) 2: { 3: #if (!MF_FRAMEWORK_VERSION_V4_2 && !MF_FRAMEWORK_VERSION_V4_3) 4: return ipAddress.AddressFamily; 5: #else 6: return (ipAddress.ToString().IndexOf(':') != -1) ? 7: AddressFamily.InterNetworkV6 : AddressFamily.InterNetwork; 8: #endif ...
I finally got what I wanted to add some time to my Library M2Mqtt : support for the SSL / TLS protocol !
With this new feature , you can now connect to a MQTT broker also using SSL / TLS (for .NET Micro Framework only up to TLS1.0 ) to take advantage of its key features: data encryption and server authentication through an X509 certificate (client authentication is not supported) .
To leave free choice to the developer wanted to or not to include this feature in his project ,I tied everything to the compilation symbol "SSL" which must be defined to add such support. In this way, for some platforms with less memory (see Netduino or FEZ Cerberus in the case of .NET Micro Framework ), you can exclude it , remembering to remove all references to assemblies that run the SSL / TLS.
Of course , as well as on CodePlex, the update is also available on Nuget !
As soon as possible, I will write a new post in which I describe an example of using secure connection with an MQTT broker like Mosquitto !
Today I published my M2Mqtt library on Nuget, besides being already available for some time on CodePlex.
I've included the compiled assemblies for the. Net Framework 4.0 and 4.5 and for the. NET Micro Framework 4.2 and 4.3.
I hope I have done something pleasing for those who until now have used it by downloading the source files directly from CodePlex.
I have made a "small" update on my MQTT client (now at version 1.1.0.0), adding an additional constructor on MqttClient class which has the host name of the broker as parameter (adding to the constructor that provides only the address IP). Such a constructor may be useful in all those cases in which you use a MQTT public broker , such as the Mosquitto test server that is at test.mosquitto.org.
1: public static void Main()
2: {
3: MqttClient client = new MqttClient("test.mosquitto.org");
4: ...
5: ...
6: }
The MQTT client, which I released on CodePlex that can be used with all versions of the. Net Framework specially with NET Micro Framework, was published with a blog post on Coding4Fun on Channel9 by Greg Duncan.
I have just posted a new little CodePlex project: M2Mqtt.
It is a MQTT client (Message Queue Telemetry Transport) that can be used on all .Net platforms, obviously focused on. NET Micro Framework.
MQTT is a protocol for M2M (Machine to Machine) as part of the Internet of Things and for which lately has been a process of standardization by OASIS. Suffice it to say that thanks to his remarkable "lightness", was chosen as the protocol for the exchange of messages through the Facebook Messenger.
For further information please refer to the official website MQTT but I will not fail to publish as soon as possible a series of articles related to this protocol and to the use of the library that I just released.
I recommend .... stay tuned!
After abandoning support for the development of smart devices with the. Net Compact Framework in Visual Studio 2010, Microsoft seems to be back on his feet. In fact, Visual Studio 2012 will return to support it, especially in view of the release of Windows Embedded Compact v.Next. In September, some news will be announced about the roadmap of the. Net Compact Framework. This information can be read on the Microsoft Connect site at the following link for an open request by a developer who wondered why in Visual Studio 2010 there wasn’t support for the development of Windows CE. Net Compact Framework. An official voice of the Microsoft responded well ... Hi folks, In the first quarter of 2013, we plan to provide tooling for Visual Studio 2012 to create apps for Windows Embedded Compact v.Next. We’ll be announcing more details in September, including the roadmap for .NET CF. You can find more details this Fall in the Windows Embedded Compact website at http://www.windowsembedded.com. thanks, ...
View this page in another language:
