Content deleted Content added
WP:EL / linked pages don't contain information supporting this statement / unsourced and promotional |
Rescuing 3 sources and tagging 0 as dead.) #IABot (v2.0.8 |
||
Line 61:
In February 2011, Novell posted a preview of the Mono 2.12 C# compiler, the first open-source compiler for .NET Micro Framework.<ref>[http://forums.netduino.com/index.php?/forum/12-mono/: Experimental Mono support for Mac/Linux]</ref>
On 23 January 2017, after numerous attempts (<ref>{{cite web |title=Manifest for .NETMF (the current state and the future we want for it) |url=https://github.com/NETMF/netmf-interpreter/issues/491}}</ref> and <ref>{{cite web |title=Future of .NETMF (take #999999) |url=https://github.com/NETMF/netmf-interpreter/issues/527}}</ref>) to revive .NET Microframework project and bring it to community governance and a period of work "in the dark", a group of embedded systems developers publicly announced .NET nanoFramework as spin-off of .NET Micro Framework.<ref>{{cite web |title=The name’s Framework, nanoFramework |url=https://nanoframework.net/2017/01/23/my-name-is-framework-nanoframework/ |access-date=2019-02-22 |archive-date=2019-02-22 |archive-url=https://web.archive.org/web/20190222152330/https://nanoframework.net/2017/01/23/my-name-is-framework-nanoframework/ |url-status=dead }}</ref> A major rework on the build system, an easier way of adding new targets, a modernized API following [[Universal Windows Platform|UWP]], a Visual Studio extension with all the tools required for managing targets, full development experience from coding to debugging on the native code and support for ARM Cortex-M and ESP32 were the key differences at that time. On 12 October 2018 the first official release of the class libraries and firmware images was announced.<ref>{{cite web |title=nanoFramework v1.0 is official! |url=https://nanoframework.net/2018/10/12/502/ |access-date=2019-02-22 |archive-date=2019-02-22 |archive-url=https://web.archive.org/web/20190222152201/https://nanoframework.net/2018/10/12/502/ |url-status=dead }}</ref>
On 16 December 2016, GHI Electronics announced their own implementation of Micro Framework called TinyCLR OS, citing lack of maintenance of NETMF by Microsoft.<ref>{{Cite web |url=https://www.ghielectronics.com/community/forum/topic?id=24044# |title=Introducing TinyCLR OS: a new path for our NETMF devices |access-date=2017-07-28 |archive-url=https://web.archive.org/web/20170728203332/https://www.ghielectronics.com/community/forum/topic?id=24044# |archive-date=2017-07-28 |url-status=dead }}</ref> On 7 July 2017 GHI announced 5th preview of TinyCLR OS.<ref>{{Cite web |url=https://www.ghielectronics.com/community/forum/topic?id=24580# |title=Fifth Preview of TinyCLR OS Core Features and Porting |access-date=2017-07-28 |archive-url=https://web.archive.org/web/20170728202902/https://www.ghielectronics.com/community/forum/topic?id=24580# |archive-date=2017-07-28 |url-status=dead }}</ref> On 2 February 2018 GHI announced 8th preview of TinyCLR OS.<ref>{{Cite web |url=http://tinyclr.com/tinyclr-os-eighth-release-fez-hydra-wi-fi-and-cortex-m7/# |title=TinyCLR OS Eighth Release: FEZ Hydra, Wi-Fi, and Cortex-M7 |access-date=2018-02-15 |archive-url=https://web.archive.org/web/20180309184128/http://www.tinyclr.com/tinyclr-os-eighth-release-fez-hydra-wi-fi-and-cortex-m7/# |archive-date=2018-03-09 |url-status=dead }}</ref> On 5 April 2018 GHI announced 10th preview of TinyCLR OS.<ref>[https://forums.ghielectronics.com/t/tinyclr-os-tenth-release-bugs-rtc-and-stm32f7/21327 TinyCLR OS Tenth Release: Bugs, RTC, and STM32F7]</ref>
Line 96:
===MikroBus.Net===
The MikroBus.Net Quail is an STM32-powered development solution for building hardware prototypes with click boards and C# managed code. It brings together Mikroelectronika click boards and the Micro Framework for embedded devices (NETMF).<ref>
==See also==
| |||