NETMF 4.3 QFE2 released

The changes to NETMF 4.3 to make it work with VS 2013 have been released from its beta state and is available on Codeplex.   This will give us room in the next few weeks to start a new beta with more cool things coming.  Stay tuned.

Comments

• Anonymous
  January 28, 2015
  That's great, but what exactly is new? Which bugs are fixed? What is the roadmap? Can we expect more "Realtime" and "Performance" features like AOT, JIT and the ability to write native interrupt handlers in C# for the future?

• Anonymous
  January 28, 2015
  The comment has been removed

• Anonymous
  January 29, 2015
  Great job! Please provide support for Visual Studio 2015 at the BUILD event.

• Anonymous
  January 29, 2015
  Hi Colin,  I know that its early days and haven't been back long - but can you publish more details on the changes to the network stack....we have been having issues with a product due to the stack and am wondering what direction this might be heading in so we can start to plan if we end of life the project or we look to moving it to the new stack.

• Anonymous
  January 29, 2015
  HI Mike,   There were latent timing issues with the integration of LWIP into a NETMF thread.   We are investigating inserting a small RTOS to support separate threads for NETMF and LWIP and initial results are promising.   Colin

• Anonymous
  January 29, 2015
  Thanks to the NETMF team for starting to move this platform back into the daylight! Just wanted to share that we are also suffering from the instability of the networking stack, which has jeopardized release of our commercial product based on NETMF (a system for automating truck logistics). There is a lot of hope riding on these recent tidbits of news about firming up the networking and all. However, I think that what we are all looking for is a little bit more concrete roadmap for this platform with a clear understanding of what to expect and when. I realize that committing to specific dates is extremely difficult due to the elusive nature of the software problems, but we (the users of NETMF) are finding ourselves in even more precarious situation, since we have to plan releases of our products that depend on the stability and capabilities of the platform for which we have very little information.  Don't get me wrong - the information flow about NETMF has been improving lately, but it is still nowhere near the level when a CTO could feel comfortable pitching it to the CEO or to the Board as a basis of a new product. In our particular situation we have considered all kinds of mitigation scenarios, including scrapping the current project and starting from scratch using embedded Linux - believe me, this is not a conversation that you want to be having with your CEO after investing over 18 months of work of several developers into it. In a nutshell, we need clarity, releases timeline and assurances that there will not be another "paradigm shift" in a few months leaving us to pick up the pieces. Again, I really appreciate this renewed commitment to NETMF, because it feels much better now than it was 6 months ago.  We just want this train to be moving even faster and wouldn't mind seeing its schedule ;) Sincerely, Alex O.

• Anonymous
  January 29, 2015
  It sounds as if you are on the right track, keep up the good work netmf-team!

• Anonymous
  February 04, 2015
  Hello I don't see the Porting Kit for NETMF 4.3 QFE2 release version. Is the last version of the Porting Kit compatible with this release ? If so, could someone provide the link ? Thanks

• Anonymous
  February 11, 2015
  The comment has been removed

• Anonymous
  April 29, 2015
  The templates in the netmfvs2013.vsix 4.3.2.3 (1/9/2015) which came from netmf-v4.3.2-SDK-QFE2-RTM.zip (new Netduino Plus 2 Application) seem to cause a new Netduino plus 2 project to reference SecretLabs.NETMF.Hardware version 4.2.0.0 instead of 4.3.1 and SecretLabs NETMF.Hardware.Netduino 4.2.1.0 instead of SecretLabs NETMF.Hardware.NetduinoPlus 4.3.1.0. Is this a MS issue or a SecretLabs issue?   or my issue?

• Anonymous
  April 29, 2015
  Hi John,    It appears that you are using the Netduino 4.2 SDK which is why there is a mismatch in assembly versions reports.   There is a 4.3 Netduino SDK on the site - it is not set up as the default SDK so you have to find the pinned forum page that links to it.   I'd put a pointer in here but the Netduino.com site seems to be down at the moment. If you get that version of Chris' SDK you should be fine.  

• Anonymous
  April 29, 2015
  Thanks for the quick reply Colin.  I did have the 4.3 Netduino SDK installed and the project referenced dlls from it for SPOT, etc but not for the hardware.  We installed things on another machine and things worked fine.  One difference was that I was running the original VS 2013 DVD installation on the machine that didn't work right and the other machine that worked was running update 4.  Installing just update 4 didn't fix things but removing the netduino SDK and .net micro sdk, and reinstalling them after the update 4 was installed fixed the problem.

• Anonymous
  April 30, 2015
  Interesting.   I am not sure what differences there are with the DVD installation.  I'm glad you got past it.