.NET Micro Framework Embraces Open Source
First, quoting Sina:
</p>
——————————————————
November 16 news, according to foreign media reports, Microsoft today released .NET Micro Framework 4.0 at the Los Angeles Professional Developers Conference (PDC). This product is open source, released under the Apache 2.0 license, and will be widely used in the embedded field.
In the .NET Micro Framework environment, development and execution environments with resource constraints were initially started by Microsoft's internal business accelerator, but have recently moved to the development department to align more closely with Microsoft's development efforts.
This enables .NET Micro Framework to become a seamless experience, providing developers with a broad programming model and tool chain for a single solution, from small smart devices to servers and the cloud.
This includes source code for almost all products, including .NET Micro Framework and the CLR code itself. Developers can access the base class libraries that are implemented.
However, embedded programmers shouldn't get too excited. The complete code is not provided. For example, the key TCP/IP stack from third-party EBSNet and the cryptography library cannot be released. As for the Cryptography library, it is currently not included in the source code. Microsoft says this is because their use extends beyond the scope of .NET Micro Framework. Customers who need access to cryptographic function code will find that these libraries can be replaced.
——————————————————
After 4 versions, Microsoft has finally come around. .NET MF is finally open source. I predicted this back when .NET Micro Framework was still at 1.0. This kind of hardware-related stuff won't work if it's not open — you can't play alone.
Like Windows CE, the kernel code must be open. Otherwise, third parties face numerous difficulties when porting to hardware platforms. Code often crashes inside someone else's function. With source code, you can take a look and fix the problem. Without code, you have to call Microsoft support. Setting aside cost issues, phone support is inherently inefficient. With slow response, Android and iPhone catch up. Microsoft has no choice — it wants to be an open platform without making hardware.
This also proves an "unwritten rule": never use a Microsoft product before version 3.0. Version 4.0 is usually mature. After years of折腾, .NET MF seems to have finally matured. Can't find the source online yet — once I do, I'll download it and play around.
</span>