-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Samples
🍬 Code samples from the nanoFramework team used in testing, proof of concepts and other explorational endeavours (by nanoframework)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
nanoFramework.WebServer
:package: Web server for nanoFramework packed with features: REST api using attributes, multithread requests, parameters in query URL, static files serving.
-
lib-nanoFramework.System.Net.Http
Discontinued :package: nanoFramework System.Net.Http class library [Moved to: https://github.com/nanoframework/System.Net.Http]
Connecting to Azure IoT is easy with library support for Device Provisioning Services (DPS), SAS token and certificate authentication, Cloud to Device (C2D) messages, Device to Cloud (D2C) messages, remote function calls, twins, for clients and modules! There is also full support for IoT Plug & Play.
AMQP,
TcpClient,
and UdpClient.
TLS and secure HTTP is supported. You will find examples in the sample repository. The samples demonstrate how to use WebRequest, HttpListener as well as how to make low-level REST calls to Azure services.
HttpClient is fully implemented and is a very convenient way to call REST services. HttpClient works just like the full .NET implementation. You'll find the source in the .NET nanoFramework System.Net.Http repository.
Worth noting that the JSON content above it's presented as a simple string to simplify the code. There is a json library available to help with serializing and deserializing from/to C# classes, even the most complex ones.
The title is correct, we kept the core ideas of the full ASP.NET framework. We shrink everything possible, but kept the controller, security authentication, and attribute decoration concepts. You'll find the source in the .NET nanoFramework WebServer repository. Features include:
URL decode/encode
There is support for an MQTT client in .NET nanoFramework. You'll find the source in the .NET nanoFramework MQTT repository. The usage is the same whatever version is used, 3.1, 3.1.1, and 5.0 are supported. There are differences between v3.1.1 and v5.0. Version 5.0 brings more control and additional properties. For convenience, V5.0 properties are shown from Intellisense as v5.0 only. If you try to use v5.0 properties with the v3.1 or v3.1.1 protocols, they'll be ignored.
WebSockets can be used as a client, a server, or both at the same time. You'll find the source in the .NET nanoFramework WebSockets and SignalR repositories.
WebSockets can be used as a client, a server, or both at the same time. You'll find the source in the .NET nanoFramework WebSockets and SignalR repositories.
In case a DPS model is going to be used, the ID of the model has to be passed to the ProvisioningDeviceClient and DeviceClient constructor. The code above requires the following changes.