The first commercial products with the “nanoFramework inside” label (a shameless copy of the old Intel® logo) are out in the wild! Literally.They were built to perform in a demanding industry and deployment scenarios: oil fields! These devices have been developed and built by OrgPal, a leading remote-monitoring manufacturer and solution provider for the oil … Continue reading Oil tank telemetry with nanoFramework
.NET nanoFramework Blog
nanoFirmawareFlasher is here!
The nanoFramework toolbox just got a new addition: nanoFramework Firmware Flasher. This new tool is a CLI provided as a .NET Core Global Tool. And why is this so special you may ask! A .NET Core Global Tool is a special NuGet package that contains a console application. It gets installed on the developer’s machine … Continue reading nanoFirmawareFlasher is here!
NuGet, assembly and native versions
nanoFramework C# class libraries are distributed as NuGet packages to be consumed by projects. This has been like this since day one. NuGet packages are practical, easy to distribute, easy to consume, easy to update. But they had a …minor… problem. Actually, make that two… 😉 One was that the dependency between the managed assembly … Continue reading NuGet, assembly and native versions
nanoFramework Open Collective is here!
Today we have an important announcement to make: nanoFramework is now accepting donations! In the spirit of the openness and transparency that we have been following since day one, an Open Collective has been setup in order to manage these affairs. Why do we need donations you may ask… Well, let us take a moment … Continue reading nanoFramework Open Collective is here!
High Level Programming Languages for Embedded Projects
Industry expert Mark Harris just published an article on its Altium blog about "High Level Programming Languages for Embedded Projects". The article includes a thorough analysis on the topic on which .NET nanoFramework plays a key role as an excellent framework for embedded projects. Follows a copy of the original article published in June 2019, … Continue reading High Level Programming Languages for Embedded Projects
SonarCloud is on nanoFramework repos!
Code quality is something that is high in our priority list at nanoFramework. Though, being on the list is not of much use, it must be measurable and comparable against an accepted standard. For this reason, since last week we’ve been busy adding the awesome SonarCloud tool to all our class libraries repositories on GitHub. … Continue reading SonarCloud is on nanoFramework repos!
Deployment image generator
nanoFramework Visual Studio extension (both VS2017 and VS2019 versions) just got a new improvement: the ability to generate a “deployment image”. And what the heck is a “deployment image” you ask? Let me explain with a bit more detail. To run a C# application a nanoDevice must have on its storage (which is a flash … Continue reading Deployment image generator
nanoFramework ready hardware?
A quick blog post about a survey we are conducting about nanoFramework ready hardware. We get it that there is already a bunch of hardware out there that one can choose to start with or develop an embedded systems project on top of. But we've been giving this some thought internally and we are inclined … Continue reading nanoFramework ready hardware?
Welcome TI and CC3220!
The MCU family is growing larger by the day and it is time to celebrate a new vendor! Today we are adding TI CC3220SF LaunchPad™ to the growing list of nanoFramework reference targets. Yes, we’ve seen new boards added before, so why all the fuss about this one? Looking closely and it is more to … Continue reading Welcome TI and CC3220!
To deploy, or not to deploy, that’s the question…
nanoFramework class libraries are composed of a managed part (written in C#) and the respective counterpart (written in C/C++) that is part of the firmware image that runs on the target. As part of the usual development cycle there are improvements, bug fixes and changes. Some of those touch only the managed part, others only … Continue reading To deploy, or not to deploy, that’s the question…