This directory is intended for device bindings, for sensors, displays, human interface devices and anything else that requires software to control. We want to establish a rich set of quality bindings to make it really straightforward for developers to use .NET to connect devices together to produce weird and wonderful IoT applications.
This directory is intended for device bindings, for sensors, displays, human interface devices and anything else that requires software to control. We want to establish a rich set of quality .NET bindings to make it straightforward to use .NET to connect devices together to produce weird and wonderful IoT applications.
Our vision: the majority of bindings are written in .NET languages to enable portability, use of a single tool chain and complete debugability from application to binding to driver.
Our vision: the majority of .NET bindings are written completely in .NET languages to enable portability, use of a single tool chain and complete debugability from application to binding to driver.
## Binding Index
...
...
@@ -10,7 +10,7 @@ Our vision: the majority of bindings are written in .NET languages to enable por
## Binding Distribution
We are currently encouraging source distribution of device bindings. The [trimpot sample](../../sample/trimpot/trimpot.csproj) references the [Mcp3008](Mcp3008.csproj) within this repo. You can clone this repo and use the sample project reference model to a device binding or copy bindings directly into your project.
We are currently encouraging source distribution of device bindings. The [trimpot sample](../../samples/trimpot/trimpot.csproj) references the [Mcp3008](Mcp3008/Mcp3008.csproj) within this repo. You can clone this repo and use the sample project reference model to a device binding or copy bindings directly into your project.
We may publish NuGet packages of device bindings at a later date.
...
...
@@ -22,7 +22,7 @@ Bindings must:
* include a .NET Core project file
* include a descriptive README, with a fritzing diagram
* include a buildable sample (either beside the binding or a [sample](../samples))
* include a buildable sample (either beside the binding or a [sample](../../samples))
* use the System.Device API
We are currently not accepting samples that rely on native libraries for hardware interaction. This is for two reasons: we want feedback on the System.Device API and we want to encourage the use of 100% portable .NET solutions. If a native library is used to enable precise timing, please file an issue so that we can discuss your proposed contribution further.