.Net Micro Framework v4.2 RTW's

Description

[Special edition post] I wanted to get this word out, but already had something cool written for this week's hardware post* so am going to make this a quick "special edition" post. Smiley

A few months ago I mentioned that the next version of the .Net Micro Framework, v4.2, was in beta, Netduino is opening up to an wider audience with the .Net Micro Framework v4.2 release.

Well it's beta no more!

Version 4.2 RTM Today!! (Updated)

We are glad to announce today the RTM of the .NET Micro Framework version 4.2. You can download the SDK and PK as well as the all sources from our Codeplex project, client_v4_2 branch, at change number 13620. (We will be distributing 4.2 solely through the Codeplex site this time and not on downloads.microsoft.com)

Version 4.2 of the .NET Micro Framework Porting Kit provides the following new features:

  • Remote Firmware Update: The .NET Micro Framework SDK and PK now support updating your device firmware remotely.
  • Complete Cryptographic Object Model over PCKS #11: Most types and algorithms used in the desktop framework are now supported. PKCS #11 allows extensibility at the firmware level for adding new cryptographic tokens.
  • 1-Wire, PWM and A/D object model: Support for PWM and A/D operations is now provided as a standard interface. 1-Wire is provided through a community development effort
  • SNTP and FTP (client and server): Support for SNTP and FTP is provided as a community development effort.
  • StringBuilder and Regex types: Support for StringBuilder and Regex is provided as a community development effort.
  • Transcendental functions for doubles in System.Math
  • VB.NET: The SDK now support VB.NET.
  • Support for Cortex M3 devices with STM32 processor family samples: The support for the STM32 family is provided as a community development effort and features two solutions for two different development boards. See the Porting Kit for details.
  • PKStudio: PKStudio supplements SolutionWizard to create solutions for the Porting Kit environment. See the Porting Kit distribution for details. (PKStudio code can be in the community branch under %SPOCLIENT%\CLR\Tools\PlatformDesigner\PKStudio and the binaries are instead in the %SPOCLIENT%\Tools\bin\PKStudio directory ready to use)

...

You can find white papers about crypto, firmware updates, and the Codeplex distribution in general on the documentation page of the project. You can find the general documentation on MSDN. PK documentation is in the distribution, under the documentation directory (you will find there also the full .chm help

...

What I found coolest in this release (besides its VB.Net support of course) was the level of community involvement.

With this release we had outstanding community contributions. We would like to thank our Core Tech Team and all of our community. In particular, the following contributions deserve a special note:

  • PKStudio, as a replacement for SolutionWizard, was contributed by Alexandr Surkov and Igor Kiselev.
  • StringBuilder and Regex are contributed by Julius Friedman. Thanks also to Michael Schwarz for helping with this effort. (Regex from Julius to follow shortly with a Beta update).
  • 1-Wire and Transcendental functions were contributed by Richard Scott.
  • The SNTP driver is based on a managed code implementation by Valer Bocan.
  • The STM32 (Cortex M3) Port was provided by Cuno Pfister and Beat Heeb at Oberon Microsystems

We would like to thank you Alexandr, Igor, Julius, Richard. Cuno, Beat, and Valer for helping us make this a broader than expected release and contributing such important components.

Congrats to the MF team and thanks' to the community for the time and effort you've invested in this release...

 

* Admin Note: To add a little predictability to the Coding4Fun posts, I'm going to make Friday, Hardware Day. So all hardware related posts will be on Friday, giving you something fun to build over the weekend (and to keep me from making too many hardware postings too Smiley

The Discussion

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.