First of all Windows.Forms is the second most wanted feature in MONO but it is only a part of what .NET and MONO can offer. ASP.NET is the most requested feature and it is coming along quite well. In addition to that, you have database support (there are many data providers implemented including Oracle, MSSQL, DB2 and in addition to that MySQL and I think Postgres as well).
There are other features such as remoting, that you can also use and even interop with CORBA. So, when I say "Develop in Windows, Deploy in Linux" is mainly targeted towards ASP.NET, Web Services, and Remoting Services. Windows.Forms is currently targeted towards v2.0 of Mono scheduled for 2004. MONO is will work on other non X86 architectures. Currently supported architectures in various stages of development are: alpha, arm, PowerPC, s390 and SPARC and of course X86. While Microsoft didn't document a lot of things, the functionality of most of the things in the framework is something that can be implemented without knowing anything besides the stubs of the classes to be compatible with the current framework. I don't claim or want to be Microsoft's advocate, but it is in their current best interest to show that they did standartized the CLR (they did get the ECMA approval for it) and the fact that MONO exists shows that there are alternatives which makes Microsoft look even better in light of their Anti Trust case in the US and the EU. Eran ----- Original Message ----- From: "Hetz Ben Hamo" <[EMAIL PROTECTED]> To: "Eran Sandler" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, August 19, 2003 1:37 AM Subject: Re: The Mono Project > > The main issue here, that it can run on any OS including Linux, Windows, > > HPUX, SunOS, MacOS, AIX and so on. > > Not to my knowledge. All the Windows.Forms display stuff is using Wine. Have > you ever tried to run wine on non X86 system? it doesn't run.. > > > Anyhow, I was thinking about giving lecture on the subject, on .NET on Mono > > and how it can eventually give Linux yet another advantage over Windows. > > Specifically in the "Develop in Windows, Deploy in Linux" approach. > > Read my remark above please. > > > Perhaps by leveraging the awareness and knowledge about .NET and Mono we > > can find some more contributers to the project. > > > > I don't want to start a flame war because the specs for .NET came from the > > root of all evil Microsoft. > > Evil or not: > > 1. Microsoft has been granted several patents about their .Net - so Microsoft > can easily kill (if they want) the entire mono project. > 2. They have hidden quite a lot of stuff - so it's like Wine - some parts are > documented well, some poorly documented, and some - are not documented (or > it's not available for the public). > 3. It's still X86 centered - see the wine remark.. > > Good luck, > Hetz > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
