http://blogs.zdnet.com/microsoft/?p=2701
Microsoft to turn .Net Micro Framework code, support over to the community
http://blogs.zdnet.com/microsoft/?p=2701
Microsoft to turn .Net Micro Framework code, support over to the community
Thanks HD. I think that's an important notice and worth reviving the thread. After all, MS keeps complaining that a lot of the problems are because developers haven't embraced .net. Mary Jo in the blog says that's because MS is abandoning .net. She says they've slashed the development team. But, she doesn't give a clue as to what's replacing it. I'm not sure she's right. I think they're hoping to get more developers programming in .net and they can still use whatever development comes out of the user community. We won't know for sure until MS announces whether they're coming out with a new architecture. I can't find any evidence that MS is abandoning it. Six months ago, they were pushing the latest developments:
http://www.developerfusion.com/article/9576/the-future-of-net-languages/
Maybe they've got it to a point they just don't need as large of a development team anymore.
http://www.theregister.co.uk/2009/07/07/mono_microsoft_promise/
Microsoft promises no patent prosecution of open-source .NET
Ubuntu joins Debian Mono denials
Microsoft is promising not to pursue patent claims against Linux and open-source software using the open-source implementation of .NET, Project Mono.
The company has said that third party implementations of its C# and the Common Language Infrastructure (CLI) - a language runtime - will be made available under its Community Promise. The promise will cover ECMA specifications 334 and 335 - C# and CLI respectively.
That means developers, users and distributors of Mono, which implements the C# and CLI specs, should be protected against possible action by Microsoft.
There was no word on why Microsoft has made the promise, but it's a sudden move likely designed to limit damage between Microsoft and the community over Mono.
http://www.theregister.co.uk/2009/07/07/mono_splits/
Open-source .NET splits for extra Microsoft protection
http://blogs.zdnet.com/microsoft/?p=3069&tag=nl.e550 > Too many .Nets, too little time?
Microsoft’s overzealous .Net branding campaign is a pretty much a thing of the past. But that doesn’t mean the .Net confusion is completely over.
Microsoft’s attempt to juggle too many .Nets is coming home to roost with testers writing workflow-centric apps and services that can be hosted in the Azure cloud. In a posting to the Azure Services Platform blog last week, Microsoft officials admitted that .Net Services was based on a different, older version of .Net — and that the newer version wouldn’t be ready in time for Azure’s official launch (which is expected this fall).
Thanks, again, HD. I'm thinking that the first 2 articles give a hint of what's really going on. Microsoft likely turned it over to the community not because they're abandoning it, but because it's secrets are HARDLY secrets anymore, that's why we have Mono. Since you have to give developers enough clues so they can use it, it becomes a lot easier to reverse engineer it. It's not like Visual Basic was some big mystery when MS was working with it in Visual Studio.
That 3rd article gives another clue that MS isn't dropping .net, yet. Since it's going to be part of the Visual Studio 2010 release. I noticed that article was also by Mary Jo Foley, whose article saying that MS is dropping .net you linked to above. Yet, Mary Jo, who's supposed to be so well connected, STILL hasn't told use what's replacing .net. I'll believe that .net is dead when someone announces it's replacement. !
You must log in to post.