Everything what has the processor inside is considered to be a module here.
Discontinued products:
Current products:
For an overview of their features and differences, see the big comparison table.
Expected products:
Others and specialized products:
These modules are either intended for specialized applications, or I do not have enough info about them to include them in mainstream products for developers. If you do have and want to share, let me know.
The board comparison table will be available later.
.NET Micro Framework is slowly reaching the consumer market as well. Here are the first products available (exluding SideShow displays only and devices with MSN Direct service, which is not available in Europe):
Microsoft has published document (PDF, 539 kB) introducing these products, as well as other concepts and prototypes shown at Nuremberg exhibition this year.
If you want to use some native code or have the .NET Micro Framework on your own processor, you have to port it there. You will need the .NET Micro Framework Porting Kit for this task, which is available for about $600 at Microsoft Store. There are practically two tasks you might want to handle:
In this case, you just need to add some feature to the existing framework requiring native code, perhaps some unsupported hardware access, or just some fast computation. Unfortunately, dynamic loading and binding of native code is not supported at this time. Adding interop native code requires creation of a custom image. Typically you need a BSP (board support package) from your hardware vendor, create a managed interface to the native code you would like to add, generate native stubs from it using Visual Studio, implement them in native code and build new HAL/PAL using the native platform compiler. Then you can call your method using [MethodImpl(MethodImplOptions.InternalCall)] attribute.
In such case, good luck to you! :-) You will need to verify if support exists for your platform (e.g. ARM), and then use the Solution Wizard included in the Porting Kit to create a new solution or derive from existing sample. Follows the implementation of HAL and/or PAL functions for BSP and building it using the native platform compiler. After testing your BSPs, you would need to sign a porting agreement with Microsoft to be able to sell your devices. There is a licence fee for the devices sold, which was heard (by Peter, thanks for sharing) to start around $2 (not confirmed).
For porting kit related questions, try the microsoft.public.dotnet.framework.microframework.porting news group (web access), or write directly to netmfbiz@microsoft.com.