UPDATE: Microsoft has a new community site for .Net 3.0 – NetFx3 – with lots of information and some popular RSS toolkits.
In this MSDN blog Somasegar explains that many developers were confusing the tecnologies, so they decided to rename WinFx to .Net 3.0. What this really means is that the Windows Presentation, Communication, Workflow and CardSpace Foundations will be merged with all the .Net 2.0 components (C# 2.0, ASP.Net, MWF, etc…) and will then be called .Net 3.0.
They plan to release the .Net Framework 3.0 with Windows Vista and it will be backward compatible with Windows XP and Windows 2003, so developers can use their current tools to develop Vista applications. Note that Visual Studio “Orcas”, due to 2007, and LINQ support have nothing to do with this, .Net Framework 3.0 will be using the C# 2.0 so there wont be any C# 3.0 features, LINQ included. In the end I think they will rename C# 3.0 to C# 4.0 just to avoid massive confusion. Visual Studio “Orcas” will be the next major release of the CLR and will include Visual Basic 9.0, C# 3.0 and LINQ – LINQ has a May CTP here.
I do not know where this will place Mono, I don’t think Mono will be able to implement all this Windows * Foundation things, either because they are very Windows specific or because of license and patent issues. Something I would like to hear/read Miguel to comment.
I hope that mono will be implement the complete .net 2.0 framework and the main
language functionality (c#, vb.net…)
The goal isn’t to implement windows specified things like wpf or c#3.0 future features… Its important for cross platform developer like me that you
implement the general functionality of .net 1.1 AND 2.0 and the windows forms.
I know, that the mono team do heavy work, but mono isnt an alternative to .net now.
So, i wish you successfully
work for the next months
k00ni
ps.: sorry for my poor english.
Hi,
well but the windows presentation foundation will be the
next windows forms. So in the future more and more developers will use the windows presentation foundation, or maybe the current winforms will be extended with windows presentation foundation stuff.
So personally I believe that we won’t have a platform independant gui framework beside gtk# in the future.
The winforms become better and better but till it is perfectly working, and also
winforms 2.0 is working at all the windows gui framework will depend on the windows presentation framework. I don’t know, if it is possible to port wpf or wcf and so on. But as you already said this
is not important for Mono.
Maybe Mono should go another way: Not trying to get asp.net, winforms, wpf, wcf and so on working. Instead of this: developing complete new technologies. A platform
independant gui framework (gtk#) and writing new web frameworks too, not implementing asp.net.
The only thing that should be implemented is the c# language and the basic .net framework.
Microsoft will extend the .NET framework in the future and mono really can’t implement everything. And there will be more and more mono can’t implement because of the amount of stuff in .NET. So go
your own way and make it a linux platform, which can be used on windows too. Not making a windows platform working on linux.
Greetings
Mike
Just thought I’d add a little more to the “crossplatform GUI framework” side of the discussion.
Two days ago Richard Dale announced that the Qyoto C#/mono bindings are very
close to being complete. See here:
http://www.kdedevelopers.org/node/2090
Qyoto is a binding to Qt — a very top-notch GUI framework that’s crossplatform. Things like Google Earth and
Opera Web Browser are written in it.
Anyways, you can already develop C++ Qt applications in Visual Studio with Trolltech’s plugins. While the development is all being done on mono and Linux
there’s nothing inherent in the Qyoto bindings that would prevent them from working on Win32 with MS’s CLR.
I wouldn’t be surprised if Trolltech got behind Qyoto, even.
Full
disclosure: I very much like Qt development, mostly because of the thorough documentation.
Hi all,
I think Mono developers should not be discouraged by
Microsoft’s advancements in .NET Framework. Linux needs a modern programming language like c# and a modern runtime environment. Mono should go on, try to implement all there is in .NET 2, but apply
that special Linux touch of simplicity to all things. Windows security is still to complex to really work, and the way I see it, it will only get even more complex and more hard to keep in control.
Maybe Mono should be to Linux what .NET will be for Windows. I just want to encourage every Mono developer to keep up the very good work, to go on and finish what they have started. It’s a very good
product and I can’t wait to see it grow up to full maturity.
Radu.
Hi All,
I think that if mono can develop the avalon
portion of .net 3.0 it will be a huge complement to mono. After studying xaml and the code behind concept applied to a platform UI I think it simplifies building the UI for an application and
increases a developers productivity. Anyway keep up the great work.
I never use mono, but I always wait mono to grow and fully compatible
with .Net 2.0. But after I heard that Windows Vista will launch with all new .Net framework, I think I will migrate o mono rather than staying on Ms .Net framework. The new Windows Vista requirements
is too heavy for my Computer and most office in Indonesia, so I really have to consider migrating my application to mono.
The only one reason I haven’t migrate to mono is there is no mono IDE
on Windows.
Keep growing and have fun.
It won’t be just Mono suffering, Microsoft itself is going to suffer
too. What are they supposed to call the Compact .NET Framework? 3.5? Even when there’s no WinFX to make up the “3”?
http://www.petitiononline.com/winfx/petition.html