Hello!

It’s been a while since the .NET Micro Framework team has provided an update about the project.  Well the team is here and has been busy gathering feedback from the community, thinking about future direction of the project and at the same time starting to work on some of the base functionality that is currently blocking many of you.  Right now the team is working on Visual Studio 2013 integration and we are expecting to have some bits for the community to try in the next few weeks. 

We are also looking at how we can make things easier from an OSS community engagement perspective.  We want to make sure .NET Micro Framework is an OSS project.  You might have seen temporary permission changes on our Codeplex site as an initial step towards that objective.

 Let’s not forget the netmf.com website. The site is due for some updates and we are exploring options at this point.

 We’re excited to be moving the gears again and in the coming weeks and months we will continue posting the work and progress the team is making.  So stay tuned for additional details.

Comments

  • Anonymous
    June 28, 2014
    It's greate to read this Sal ! We are waiting for great news from .Net Micro Framework team ! Paolo.

  • Anonymous
    June 28, 2014
    Regarding netmf officiale web site, it could be great to have the forum integrate with all other MSDN forums. Now it seems to be a product outside the Microsoft offer. Paolo

  • Anonymous
    June 29, 2014
    We have been standing by for quite some time, looking forward to move on!

  • Anonymous
    July 01, 2014
    This is great news!

  • Anonymous
    July 03, 2014
    The comment has been removed

  • Anonymous
    July 04, 2014
    Finally Microsoft is getting back into the Internet of Things world that is going to be pivotal in this decade. We are using NETMF to design commercial products and Microsoft's previous lack of commitment to NETMF was a major obstacle not letting us to move forward quickly. I am excited to see this renewed commitment from Microsoft and hoping that it is not just a fleeting interest this time around. I am cautiously optimistic, but the emphasis is on the word "cautious" until we see some new developments actually released to the community. Thanks and good luck to the team!

  • Anonymous
    July 11, 2014
    Is support for Visual Studio 2013 in the works?

  • Anonymous
    July 11, 2014
    Thank you for the comments. Yes, we are working on Visual Studio 2013 support and we should have preview bits to release to the community soon, likely in the next few weeks. Thanks, Salvador

  • Anonymous
    July 14, 2014
    So, I was not the only one to think that .NET Micro was dead. I'm still not totally convinced as I can't find a single word about it in the official Microsoft IoT pages. Still the same Windows centric message. I still believe the best Microsoft product is .NET and not Windows. Check how both Xamarin and Unity can leverage from it. The Microsoft OS and Office groups left Microsoft in the awkward position that is now.

  • Anonymous
    July 18, 2014
    I suppose the main sticking point from my point of view is to make the garbage collector more deterministic so we can make more use of the heap and reduce the 20ms cycle time. Let's get more quadcopters out there and breath some life into gadgeteer

  • Anonymous
    July 31, 2014
    That's really nice that .NET Micro is not totally dead. I am looking forward to see some new features soon.

  • Anonymous
    August 05, 2014
    Sal, I  think not dead would imply seeing updates at least once a month, assuming you were not in the layoffs.

  • Anonymous
    August 13, 2014
    i'm tired of waiting ... "should have" "likely" "next few weeks" With this MS commitment .Net micro is dead for sure ...

  • Anonymous
    August 15, 2014
    Please. After a flurry of initial work, it looks like the Micro Framework is dead. We need definitive comment from MS one way or another.

  • Anonymous
    August 18, 2014
    NETMF is still alive.  As far as the Visual Studio integration, the team hit a couple of issues with code signing and the build environment.  As soon as we resolve those issues we will post an update. Thanks, Sal