iot
Avalonia
Our great sponsors
iot | Avalonia | |
---|---|---|
7 | 254 | |
2,106 | 23,749 | |
1.3% | 2.8% | |
8.5 | 9.9 | |
3 days ago | 3 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
iot
-
Windows IoT Core (C# / XAML) port
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.
-
Raspberry Pi 3B generates jittery PWM.
Try the same program but with a hardware PWM library, e.g. https://pypi.org/project/rpi-hardware-pwm/
-
#JulyOT 08: .NET nanoFramework GPIO, I2C, SPI and other IO support
.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.
-
Is DotNet a good long term career choice?
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)
-
Is dotnet for Iot complete?
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.
- Using C# to control servo motors on raspberry-pi 4
Avalonia
-
Industrial Controller? Windows or Linux?
You might also want to look at AvaloniaUI[0] for a cross platform .NET GUI library. It is similar to WPF but much nicer to work with.
[0] https://github.com/AvaloniaUI/Avalonia
- Avalonia – Farewell to the .NET Foundation
-
AvaloniaUI: Create Multi-Platform Apps with .NET
Production user here. There's no money gotchas. They're above reproach. In fact, I've received considerable free support from their devs on GitHub Issues [1].
The Avalonia business model is based on selling XPF, which runs WPF (Windows-only) apps on other platforms. That's very interesting to big corps with existing codebases.
See my comment [2]
[1] https://github.com/AvaloniaUI/Avalonia/issues
[2] https://news.ycombinator.com/item?id=39246988#39249128
-
.NET on Linux: What a Contrast
Yes, but the portable GUI frameworks by Microsoft themselves are generally not very good, and they tend to be abandoned after a couple of years.
Avalonia is developed outside of the Microsoft corporate madness and seems to be slowly becoming the defacto cross-platform framework because it is expected to last a bit longer than a manager's attention span: https://avaloniaui.net/
- Too many Mac apps are being built with Electron
-
Ask HN: Do you have a problem you'd pay to have taken away?
Not my comment, but relevant here "The problem with compiling Skia to WASM is you'll lose any benefits of hardware graphics acceleration on the device."
(From https://github.com/AvaloniaUI/Avalonia/discussions/6831#disc... )
- Dezvoltare aplicatie desktop
- Ask HN: How to create web, mobile, and desktop apps from a single code base?
-
.NET 8 – .NET Blog
It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.
Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.
[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup
[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)
-
One Game, by One Man, on Six Platforms: The Good, the Bad and the Ugly
For desktop, Avalonia, hands down.
https://avaloniaui.net/
Open source, powered by Skia, backed by JetBrains, and quite battle-tested at this point for small to medium-sized apps. In theory perfectly capable for enterprise as well, since it's basically a spiritual successor to WPF, which has been an industry standard for about 15 years.
They're diving into mobile and WASM well, but that's more of a recent effort and I haven't tested that yet.
What are some alternatives?
nanoFramework.Device.OneWire - :package: nanoFramework 1-Wire Class Library
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
flogo - Project Flogo is an open source ecosystem of opinionated event-driven capabilities to simplify building efficient & modern serverless functions, microservices & edge apps.
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
Home - :house: The landing page for .NET nanoFramework repositories.
WPF - WPF is a .NET Core UI framework for building Windows desktop applications.
mainflux - Industrial IoT Messaging and Device Management Platform
Eto.Forms - Cross platform GUI framework for desktop and mobile applications in .NET
System.Device.I2c - :package: nanoFramework System.Device.I2c Class Library
MahApps.Metro - A framework that allows developers to cobble together a better UI for their own WPF applications with minimal effort.
System.Device.Dac - :package: nanoFramework System.Device.Dac class library
Gtk# - Gtk# is a Mono/.NET binding to the cross platform Gtk+ GUI toolkit and the foundation of most GUI apps built with Mono