Skip to content
This repository has been archived by the owner on Jun 5, 2019. It is now read-only.

Architecture

Jump to bottom
Steve Maillet edited this page Mar 25, 2015 · 15 revisions

Architecture of the .NET Micro Framework

The .NET Micro Framework consist of several loosely coupled layers that leverage and build upon one another to form the complete framework. The following layer diagram illustrates the basic layers and their relationships to one another:

.NET Micro Framework Layers

Layers

  • [Physical hardware](Hardware Layer) (not shown in diagram)
  • [CPU Support layer (CPU)](CPU Layer)
  • [Hardware Abstraction Layer (HAL)](HAL Layer)
  • [Operating System (OS)](OS Layer)
  • [Platform Abstraction Layer (PAL)](PAL Layer)
  • [Common Language Runtime (CLR)](CLR Layer)
  • Interop
  • Base Class Libraries
Interop

The interop layer is an extensible set of native code libraries that enable managed code libraries to expose functionality that is ultimately implemented in the native code of the system (much like P/Invoke does on the Mobile and desktop variants of the .NET Runtime).

Base Class Libraries (BCL)

These are the standard .NET Assemblies that are part of the framework. These provide the base types like strings and collections along with more advanced support such as networking etc...

  1. Getting Started
    1. Differences from previous CodePlex and the Porting Kit releases
    2. Contributing
    3. Coding Standards
    4. Branching Strategy
    5. Build System Requirements
  2. Architecture of the .NET Micro Framework
    1. Physical hardware
    2. CPU Support layer (CPU)
    3. Hardware Abstraction Layer (HAL)
    4. Operating System (OS)
    5. Platform Abstraction Layer (PAL)
    6. Common Language Runtime (CLR)
    7. Interop
    8. Base Class Libraries
  3. Tools
    1. MetadataProcessor
  4. File Formats
    1. PE Metadata File Format
Clone this wiki locally