Continuous(ish) Delivery of Meadow Libraries
It wasn’t too long ago that the release process for the Meadow stack was…let’s just call it horribly inefficient. From when we decided “time to ship a build” to when NuGets were available was literally measured in days. It was a process that we…
Simplifying Signal Access with Connectors
If you work directly with a Meadow F7 Feather or a Meadow Core Compute Module, accessing the hardware signals from your application is pretty simple and straightforward. The Meadow.Core stack exposes the Device.Pins collection so creating something as simple as an IDigitalOutputPort is pretty…
Why is my Meadow app always named “App.dll”?
The Meadow Core stack has a hard-coded requirement for Meadow Apps on the F7 platform to be named either “App.dll” or “App.exe”. This requirement is actually a bit of a legacy carryover from the beta days. Originally, when the Meadow stack only targeted the…
Creating Lightweight HMI with MicroLayout
If you’re working on an IoT project with a display, then you’re almost certainly wanting to show information to a user. Drawing that information using drawing primitives can be both cumbersome and non-portable. We at Wilderness Labs have released our MicroLayout library to help…
Meadow App Settings
It’s pretty common for an IoT application to need to read persistent but changeable settings at startup. Meadow applications have long supported the app.config.yaml file for settings to control behavior of the Resolver.Log, the device’s lifecycle behavior (e.g. restarting on an uncaught exception) or…
