Baby steps in opening the product

As you all know, we are working through all the issues associated with moving the product from a revenue model to an 'open' model.   That will all take place with the next release as promised earlier.  In the interim, we are taking some steps with the 3.0 product which is available for use in development and products as before.  To faciliate the broadest use of the platform, we are making the porting kit available as a free download from the Microsoft Download Center - the same place where the SDK is avilable.  There is a Service Pack that was just released for the 3.0 porting kit.  We are not going to take the time to merge those two releases at this time so anyone wanting to start with the porting kit will have to download the porting kit and then install the Service Pack over that.  The link for the new porting kit download is:  Go ahead and pass this on.  Thanks

Comments (11)

  1. Petit à petit, le .NET MicroFramework va devenir Open Source. C’est ce qu’annonçait Colin Miller, la

  2. Ray says:

    Is this still timebombed? Whats going on in the licensing department?

  3. Elze Kool says:

    The blog lines call this a baby step but I find releasing the Porting Kit for free a big step. I hope people or companies see the potential of this and build/release their port. Maybe it helps that the can peek into the source and look if they are up to the task.

    I see a new great future for Micro Framework!

  4. Colin Miller says:

    Ray asks if this is the timb-bombed verion – I should have covered that.  This is the same 3.0 time-bombed version that we had before. We have removed the time-bomb for the version that is coming out soon.  I am counting on people not wanting to ship new products on 3.0 in the next few months while we work out the licensing.  If that is not the case, we will address that on an individual basis.  

  5. Aby Mammen Mathew says:

    Its great, you have ability to try to port to other platforms and reuse functionality.

    All they are saying is 30 days for the development image deployed on the target board, if its production then might as well buy the license and get additional support from MS off course :-).

  6. Aby Mammen Mathew says:

    I was just curious, how is the deployed image time bombed, there is no RTC on the board. How does it keep track.


  7. What does this mean for older hardware? Will this open up the possibility for updating .netMF version 2.0 hardware to the most current? I’d really like to try out the latest .netMF on my old 2.0 hardware. How hard would it be to do this?

  8. Colin Miller says:

    Carlo asked about updating hardware with a 2.0 port to it.

        The best option is to check with the vendor and see if they dont have plans to update it themselves.

        The next best option is to see if that port is part the the porting kit samples.  If so, you have a good start.

        If neither of the first two options is open, you still have the option of starting your own port.  We woudl of course encourage you to share that with teh community so that everyone doesn’t have to repeat that work.  

        If you have any questions about avialable ports to specific boards, you can ‘Ask Colin’.

  9. Joe says:

    Does Microsoft plan to open to CLR source code?

    This is important for supporting processors, compilers etc. that are not currently support by the Micro Framework

  10. Joe says:

    Aby Mammen, the time is the time that the CLR is up and running. Hence it is only necessary to track the time used via the timer services built into the CLR (via hardware support). The time used/remaining is written back to the flash. This is inspected at boot, and if the time is up the CLR will not boot.

Skip to main content