Revision as of 19:31, 25 June 2007 edit Kindall (talk \| contribs) Extended confirmed users 2,152 edits mNo edit summary ← Previous edit		Revision as of 19:33, 25 June 2007 edit undo Kindall (talk \| contribs) Extended confirmed users 2,152 edits m linkify garbage collection Next edit →
Line 16: * Transparent support for storing objects in non-volatile memory Due to the constraints under which it operates, the .NET Micro Framework does have some limitations beyond those imposed by its slimmed-down libraries. For example, the platform does not support symmetric multiprocessing, multi-dimensional 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\|garbage collector]] rather than a generational approach. Support for [[interop]] (native code called from managed applications) currently has a number of limitations. The .NET Micro Framework does not support any .NET languages other than C# at this time. The .NET Micro Framework is currently supported on [[ARM architecture]] processors (including ARM7 and ARM9) and on [[Analog Devices]] [[Blackfin]]. Porting, which requires access to the .NET Micro Framework source, is performed by Microsoft and hardware partners under license from Microsoft. These partners then offer development kits and pre-built modules capable of running the framework to developers and manufacturers. Among the development kits supporting the .NET Micro Framework are offerings from [[Freescale]]'s i.MXS and EmbeddedFusion's Tahoe.

.NET Micro Framework: Difference between revisions