.NET Micro Framework: Difference between revisions

Revision as of 19:43, 25 November 2022

Revision as of 13:11, 25 January 2023

Line 41:

* Transparent support for storing objects in non-volatile memory

Due to the constraints under which it operates, the Micro Framework does have some limits beyond those imposed by its slimmed-down libraries. For example, the platform does not support [[symmetric multiprocessing]], multidimensional arrays, machine-dependent types, or unsafe instructions. The CLR is an interpreter rather than a just-in-time compiler, and uses a simpler mark-and-sweep [[Garbage collection (computer science)|garbage collector]] instead of a generational method. An ahead-of-time compiler is being developed<ref>{{cite web|url=https://blogs.msdn.microsoft.com/netmfteam/2015/10/03/llilum-roadmap-and-latest-additions/|title=LLILUM roadmap and latest additions|publisher=Microsoft|access-date=2016-06-30|archive-url=https://web.archive.org/web/20180826141116/https://blogs.msdn.microsoft.com/netmfteam/2015/10/03/llilum-roadmap-and-latest-additions/|archive-date=2018-08-26|url-status=dead}}</ref> using a modified [[LLVM]] compiler. Interoperation between managed and native code currently has several limitations. As of 2011, Micro Framework supported two .NET languages: C# and Visual Basic.<ref>[httphttps://blogswww.msdnasp.com/b/vbteam/archive/2011/06/08net.pe/reseller-windows.html#micro-framework-v4-2-support-for-visual-basic.aspx .NET Micro Framework only supports C# and Visual Basic]</ref>

==Support==