.NET Micro Framework: Difference between revisions

Revision as of 19:29, 25 June 2007

Revision as of 19:30, 25 June 2007

Line 18:

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 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 currently 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.

Microsoft does not charge fees for developing applications using the .NET Micro Framework and makes an SDK freely available for download (however, Visual Studio Standard or better is required; the free Visual Studio Express editions cannot be used). Distributing devices that use the .NET Micro Framework does require a license, with royalties based on volume.