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!
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
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 nanoFramework plays a key role as an excellent framework for embedded projects. Check it out and join our Discord community for discussion.
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!
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 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…
After the release of v1.0 we turned a page and that is true on what concerns our GitHub repositories history. Release means tagging a point in the repository commit history. And suddenly after that all hell breaks loose on our versioning system! Continuous deployment and continuous delivery are great, but we must make sure that … Continue reading All systems green! (again)