Microsoft's. Net microframework

It took three hours Microsoft's. Net microframework Of Product Positioning and technology whitepaper. the previous text is carefully read in every sentence. Of course, some of the content is not understood (even if it is written in Chinese, the depth of understanding may be the same: I am not very familiar with OS and mobile development). I only read the title of appendix A and appendix B.

Extract the previous overview as follows:
Introduction
For years, Microsoft has had two offerings in the embedded space: XP embedded and Windows CE. these operating systems have formed the platform for processing successful devices, such as PDAs, smart phones, automatic teller machines, and network switching equipment. microsoft introduced. net Framework, which brings the power and reliability of managed code to scale from large servers to embedded devices. however, specified devices are still too small/resource constrained to support these platforms. to serve the market for even smaller devices, Microsoft has developed a new platform Microsoft. net micro framework. (. net MF ). the. net micro framework addresses this untapped area by providing a small, efficient implementation of. net runtime for smaller devices. this has great advantages to developers who can maintain the same managed code, use the same world class tools, and continue to participant in the world's largest developer community.

List areas of interest (including some weak knowledge that should be learned from this document ):
1. Microsoft's continuum of processing capabilities for embedded applications
Windows xpe (potentially with the. NET Framework)
Windows CE (potentially with the. NET Compact framework)
. Net micro framework (bootable runtime)
2.: bootable
The microframework provides a subset of full OS features, so it does not require an OS and is referred to as a 'bootable' Runtime
. Net MF does not require the support of the underlying OS, which is a great boon to embedded development: fully autonomous controllers can be developed on Micro Devices. can it replace assembly and C/C ++ ?! If you can use. Net for weak current development and smart control, that's an exciting opportunity!
3 system requirements
Currently the Platform runs on several ARM 7 and ARM 9 processors. the suggested minimal memory configurations at present are 300 k ram and 1 meg of flash. the devices also need to have serial or USB support to support downloading and debugging the applications during development.
However, WinCE requires 12 m ram, and only 300 k is required. Generally, small devices can easily meet this requirement.
4. Visual Studio Integration
This integration supports full emulation of your device on the PC, building and deploying the assemblies to the device, and debugging the code running on the device through USB or serial connections