You can edit almost every page by Creating an account. Otherwise, see the FAQ.

.NET nanoFramework

From EverybodyWiki Bios & Wiki






Script error: No such module "Draft topics". Script error: No such module "AfC topic".

.NET nanoFramework
Developer(s).NET nanoFramework Contributors
Initial release2016; 8 years ago (2016)
Stable release
1.7.3.3 / February 2, 2022; 2 years ago (2022-02-02)
Repositorygithub.com/nanoframework
Written inC++ and C#
Engine
    PlatformARM, Extensa
    Available inEnglish
    TypeSoftware framework
    LicenseMIT..[1]
    Websitenanoframework.net

    Search .NET nanoFramework on Amazon.

    .NET nanoFramework is a free and open-source software platform that enables writing C# applications for constrained embedded system devices. It's an independent project, not part of Microsoft nor affiliated to it. Allows using a variety of microprocessors from several vendors, like STMicroelectronic, ESP32, Texas_Instruments, NXP_Semiconductors or Raspberry_Pi.

    History[edit]

    In August 2016, the .NET nanoFramework project was started by José Simões and group of NETMF enthusiasts as a spin-off of .NET Micro Framework[2] [3].

    By January 2017 public announcement of the project was made and GitHub organization was made public[4]

    In December 2017 the Visual Studio extension was published allowing for the first time coding, deploying and debugging a .NET nanoFramework project.

    In October 2018 the first stable release was published.

    Espressif (the manufacturer of ESP32 lists .NET nanoFramework as one of the official 3rd party SDKs[5]

    In April 2019 the extension for Visual Studio 2019 was published.

    In September 2020 the project joins the .NET Foundation.

    In February 2021 was published the Unit Test Framework library, compatible with Visual Studio Test Framework.

    In August 2021 was published the Microsoft Azure IoT SDK.

    In October 2021 support for the ESP32-S2 series was added.

    Hardware[edit]

    The project does not have proprietary or closed source hardware. Instead it provides firmware images that run on multiple hardware from multiple vendors. There are ready to flash images for:

    • ST Microelectronics (STM32F0/F4/F7/L4/H7 series)
    • ESP32 like the Wrover Kit, ESP32 DevKit-C, Lilygo TTGO
    • ESP32-S2 like the FeatherS2, TinyS and ESP32-S2 Kaluga 1
    • M5Stack Core, Stick and Atom
    • Texas Instruments CC3220, CC1352R/P
    • NXP MIMXRT1060-EVK

    Supported architectures[edit]

    As of 2021, the .NET nanoFramework was supported on ARM architecture processors (including Cortex-M0, M4 and M7), Tensilica Xtensa LX6 and LX7 dual-core microcontrollers and single-core RISC-V microcontrollers.

    Companies using .NET nanoFramework in commercial products[edit]

    NuGet packages[edit]

    There are over 170 NuGet packages with class libraries, drivers and IoT device bindings available for developers to speed up their development. These have been downloaded over 1 million times.

    IoT Show episodes[edit]

    There have been a series of episodes on Channel 9 IoT Show featuring .NET nanoFramework.

    Blog posts, news articles and other appearances[edit]

    .NET nanoFramework has been the subject of posts in several blogs.

    "Show .NET" series in Microsoft .NET Blog[edit]

    Other mentions in blogs and podcasts[edit]

    Articles in tech magazines[edit]

    Has been featured in .NET Foundation Project spotlight series.

    See also[edit]

    Some use of "" in your query was not closed by a matching "".Some use of "" in your query was not closed by a matching "".

    References[edit]

    1. ".NET nanoFramework".
    2. "Manifest for .NETMF (the current state and the future we want for it)".
    3. "Future of .NETMF (take #999999)".
    4. "I'm Framework, nanoFramework".
    5. "ESP32 Third party SDKs".
    •  This article incorporates text by José Simões available under the CC BY-SA 3.0 license.

    References[edit]


    This article ".NET nanoFramework" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:.NET nanoFramework. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.