Slashdot Mirror


Microsoft Open Sources .NET Micro Framework

An anonymous reader writes "Back in July, Microsoft announced it was making .NET available under its Community Promise, which in theory allowed free software developers to use the technology without fear of patent lawsuits. Not surprisingly, many free software geeks were unconvinced by the promise (after all, what's a promise compared to an actual open licence?), but now Microsoft has taken things to the next level by releasing the .NET Micro Framework under the Apache 2.0 licence. Yes, you read that correctly: a sizeable chunk of .NET is about to go open source."

4 of 320 comments (clear)

  1. Re:Mono? by LWATCDR · · Score: 4, Informative

    Nope this framework is for mobile devices and the 360.
    Microsoft is really dieing in the mobile space right now. WinMo 6.5 Still doesn't have native support capacitive touch screens and the Mobile world is on fire with Android and of course the iPhone.
    HTC, LG, and Samsung are all developing or have released Android phones.
    Palm and Motorola are now dropping WinMo and going with WebOS and Android.
    This is one space where Microsoft is at best an also ran and really is dropping in the race for mind share.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  2. Re:My first question would be... by NervousNerd · · Score: 4, Informative

    Not quite. Visual Studio Express is free for commercial usage.

  3. Re:My first question would be... by omar.sahal · · Score: 4, Informative

    a company is made up of people

    and it is also a company, a hierarchal organization were those lower down have to do what those higher up tell them to do. Those higher up have a pattern of behavior that justifies many of the fears on Slashdot. Groklaw is full of evidence, much of which was gained through court systems from around the world.
    So to quote Wikipedia

    The base technologies submitted to the ECMA, and therefore also the Unix/GNOME-specific parts, may be non-problematic. The concerns primarily relate to technologies developed by Microsoft on top of the .NET Framework, such as ASP.NET, ADO.NET and Windows Forms (see Non standardized namespaces)

    So whats changed

  4. Re:My first question would be... by HeronBlademaster · · Score: 4, Informative

    You don't need SourceSafe at all to do any sort of .NET development. Subversion, git, CVS, etc. all work fine for .NET development.

    SourceSafe would be better off forgotten entirely.