Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The .NET MicroFramework claims to work on 64K RAM and has list of compatible targets vendors. At the same time, same vendors who ship hardware and create Board Support Packages (vendors like Adeneo) keep releasing something named Windows 7 CE BSP for the same hardware targets. Obviously the OS as heavy as WinCE needs more than 64K RAM. So, somehow .NET MicroFramework is relevant to WinCE, but how ?

Is it part of bigger OS or is it base of it, or are both mutually exclusive ?


0.00006103515625 GByte of RAM is same as 64Kbyte of RAM. I am looking for possiblity to use Microsoft development tools for small target like BeagleBone.

Nice. Now .. where is a MicroFramework for the same beaglebone ? Is it inside the released pile ?

share|improve this question
Windows CE can be built to run on a small footprint. As the CE Kernel is actually quite small, it is entirely possible to build a CE device with 64K. Of course, if you are thinking CE Mobile devices and .NET frameworks, supporting every device ever manufactured with every protocol stack and UI feature, that is a different story. – mattnz Jun 10 '12 at 22:19
up vote 1 down vote accepted

No, Windows CE should use CompactFramework.

MicroFramework is for low level electronic devices and it is now open source (v4.x). It interprets MSIL rather than performs JIT compilation. MicroFramework contains classes for controlling electronic signals, digital in/out, analog in/out, Serial, SPI, I2C, ...

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.