May, 2009

Blog - About

About .Net Micro Framework Team Blog

Welcome to the .NET Micro Framework team blog, where we’ll be posting about our experiences, ideas, and activities. Our intent is to provide the latest information about the .NET Micro Framework, to get your unfiltered feedback, to support the development of the community, and to just plain have fun.
We spend most of our time working to make the .NET Micro Framework better, and finding time to blog on a regular basis on top of that can be hard. So a number of developers, testers, and product managers from the .NET Micro Framework team will be posting here to make sure you get the latest information from a variety of perspectives. Occasionally MVPs and Microsoft employees in other groups will join in as well. 
By the way, this blog is usually not the best place to get immediate help with a problem you’re having. Support for specific .NET Micro Framework issues is best obtained through Microsoft product support services, our discussion forum, or your board vendor.  Other .NET Micro Framework resources are available through our NETMF.com website.

  • .NET Micro Framework

    .NET Micro Framework evolution

    • 13 Comments
    Following the move of the .NET Micro Framework team to the Developer Division of Microsoft we are planning on involving the community in the future definition and development of the product by allowing access to the source code of the runtime and object...
  • .NET Micro Framework

    .NET MF moves to Developer Division

    • 11 Comments
    I need to correct a recent announcement of the demise of the Micro Framework. There are changes taking place on the team but they are all for the good. First, the product is moving into the Developer Division (Server and Tools). This is a great fit...
  • .NET Micro Framework

    Update on the transition

    • 11 Comments
    2 weeks ago now, we announced several changes - that the product was moving into Developer Division and that we were changing our business model to include access to the code. Unfortunately, we created some confusion and concern by only providing the...
Page 1 of 1 (3 items)