Home VS iot

> the core C-based stuff

Plug for https://www.nanoframework.net/

https://www.nanoframework.net/ not sure how it good in current state but for those who want use c# on esp32 - its reasonable way)

check out https://www.nanoframework.net/

You can do embedded with C#, you can work on microcontrollers, and you can make games in Unity.

Arduino, but runs .Net. https://en.wikipedia.org/wiki/Netduino Nano framework let's your write c# for esp32 and whatnot. https://www.nanoframework.net/

Yeah, that's my first thought. I've done some ESP32 programming and tried out nanoframework as my first attempt. Nanoframework is a cool project but I had some problems and ended up having to write everything in C.

Well, there is https://www.nanoframework.net/ though microbit isn't supported, but ESP32 is

On the other hand, for maximum code reuse, you can use regular .NET 7, plus .NET IoT Libraries if you need sensors/access to GPIO and so on, plus Avalonia as a GUI, which is also using XAML, but incompatible with UWP.

Try the same program but with a hardware PWM library, e.g. https://pypi.org/project/rpi-hardware-pwm/

.NET nanoFramework has support for GPIO, I2C, SPI, PWM, ADC, DAC, Serial, 1-Wire. Also the API are aligned with .NET IoT making it easy for code reuse between development on a Raspberry Pi with .NET 6.0 and an MCU running .NET nanoFramework.

You can write machine learning application using C# with the help of https://dotnet.microsoft.com/en-us/apps/machinelearning-ai/ml-dotnet. Additionally IoT development as well using C# (https://github.com/dotnet/iot/tree/main/samples/force-sensitive-resistor)

Every sensor and module out there woks with on of the standard protocols like I2C or SPI and C# supports them. But everyone wants pre-made libraries/device binding and dealing with raw I2C and SPI is frustrating. .NET also has device binding libraries and most popular devices have binding there. Meadow team is also porting their binding to Linux.