Re:Mono for Android released with Visual Studio 2010 integra...
by jimmyjazz14 on Wednesday April 06, 2011 @01:53PM
(#2416111)
They promised not to sue them, thats something I guess.
Re:Mono for Android released with Visual Studio 2010 integra...
by rbanffy on Wednesday April 06, 2011 @04:13PM
(#2416772)
I always wonder how binding that promise is.
Re:Mono for Android released with Visual Studio 2010 integra...
by jimmyjazz14 on Wednesday April 06, 2011 @04:23PM
(#2416814)
legally binding actually.
Re:Mono for Android released with Visual Studio 2010 integra...
by rbanffy on Wednesday April 06, 2011 @04:33PM
(#2416847)
Any restrictions in the promise? Does it cover all of Mono or just some parts? Does it cover all of .NET or just a subset? Does it impose any restrictions on what you do with the technology, what products you can build with it?
Re:Mono for Android released with Visual Studio 2010 integra...
by viraptor on Wednesday April 06, 2011 @07:42PM
(#2417512)
Here's the text with full list of covered technologies. http://www.microsoft.com/interop/cp/default.mspx It's not the same as the Novell deal which happened before the promise.
In short it's - as long as you conform to the specs, you're ok (no limits). On the other hand "Partial implementations are not covered.", so in practice anything could be argued here ;)
Re:Mono for Android released with Visual Studio 2010 integra...
by rbanffy on Thursday April 07, 2011 @09:06AM
(#2419289)
Does it covers supersets of the spec? I understand not all of the .NET platform is part of a formal standard.
Re:Mono for Android released with Visual Studio 2010 integra...
by krakensden on Wednesday April 06, 2011 @04:46PM
(#2416886)
It only covers Novell and its customers, IIRC.
Re:Mono for Android released with Visual Studio 2010 integra...
by SeveredCross on Thursday April 07, 2011 @01:07AM
(#2418272)
Actually, it covers all implementors (the community promise does, that is).
Re:Mono for Android released with Visual Studio 2010 integra...
by tedunangst on Wednesday April 06, 2011 @04:21PM
(#2416807)
.NET is platform agnostic, MS makes one implementation. This is actually rather like the JVM. While most people are familiar with the implementation that does run on multiple desktop platforms, there are other implementations out there (android being an obvious one, blackberry's another, IBM has several).
Anyone wishing to run .NET code can write a VM for it (like mono). As hard as this sounds, it's still easier than reverse engineering all of MFC (like wine).
Re:Mono for Android released with Visual Studio 2010 integra...
by bradhe on Wednesday April 06, 2011 @05:39PM
(#2417095)
Yeah, what I was trying to get at was I thought the expectation was that MS would produce/maintain them.
Re:Mono for Android released with Visual Studio 2010 integra...
by pero on Wednesday April 06, 2011 @02:07PM
(#2416182)
I think you were looking for tenets--quotes not necessary.
Re:Mono for Android released with Visual Studio 2010 integra...
by bradhe on Wednesday April 06, 2011 @02:12PM
(#2416201)
thanks, corrected.
Re:Mono for Android released with Visual Studio 2010 integra...
by leon_ on Thursday April 07, 2011 @02:07AM
(#2418409)
> Why doesn't MS commit to it?
Because MS can't sell overpriced linux licenses to mid tier businesses?
Re:Mono for Android released with Visual Studio 2010 integra...
by dman on Thursday April 07, 2011 @02:15AM
(#2418425)
Actually Microsoft has done that in the past!! - http://www.crn.com/blogs-op-ed/the-chart/208402155/microsoft...
Funnily enough I was a Novell shareholder back then. From what I remember the Microsoft sales team outsold the Novell sales team on Novell sales licenses.
One of the tenets of .NET was that it was to be platform-agnostic a la JVM but the story seems to be that they just didn't...get around...to implementing a Linux or Mac stack for various reasons (tight coupling to Win32 and existing COM servers, maybe?).
Now, Mono is reaching a state of extreme maturity. Why doesn't MS invest in this? It seems like their best way forward is dropping their single-vendor-stack mantra? Or perhaps they don't need to do so strategically yet -- once people really start demanding *nix and mac support they can "suddenly" change heart on mono?? This confuses me...but I'm not much of a strategist.