Mono Beta 1 has been unleashed onto the public. This is the first of two planned public betas before Mono 1.0 rolls out the door. The public betas are approaching an offical “production quality” state, and by 1.0 should be stable enough for corporate and coder consumption everywhere. This version includes a GAC (global assembly cache) implementation.
Mono Beta 1 Released
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Very excellent..
for those of us who wanted to get started coded some serious C# apps, but can’t stand doing development under Windows!
kudos to these guys…this has been a long time coming. Question: can Mono be installed on Windows side by side existing installations of MS .NET? Has anyone done this w/o any problems? I am anxious to DL Mono, but don’t want to break any existing installs. TIA
AFAIK you can easily install Mono and .NET at the same time.
Ive heard that some have concerns about the ramifications of using .NET technology in OSS. Anyone know where I can find an explaination of these concerns? I want to be aware of all sides before I use Mono.
You might check out the Mono FAQ section for answers reguarding Microsoft.
http://www.go-mono.com/faq.html#msft
Does it have any VB.NET support, or only C#?
I see it has ASP.NET support (pretty much exactly the same language as VB.NET except web-centric) but no mention of any VB.NET support. I remember reading a long time ago that Mono would have a VB.NET compiler but I guess that’s no longer a priority.
For info, see: http://go-mono.com/mbas.html
Crawling Mushroom Syndicate:
ASP.NET is not a programming language.
ASP.NET is the updated ASP technology, it can use either C#, VB.NET as its programming language.
mono is a must step for oss
Still no completed Mac port by the looks of it
People who complain that Mono will always be playing second fiddle to Microsoft’s implementation need to be beaten around the head with this picture: http://primates.ximian.com/~miguel/tmp/two-stacks.png
Mono is good enough that it will be able to stand on its own. Coding with it is once again a rush I haven’t felt since I first found Python. I for one will not be programming GNOME/GTK desktop applications in C for the rest of my life, any eventual cross platform compatibility is just sugar on the top. The situation is very much like NFS vs Samba. NFS sucked royally for many years and even today you can avoid a lot of pain by setting up Samba even for an all Unix network. The fact that Samba is MS’ SMB is completely irrelevant, Windows compatibility is simple a (big, admittedly) plus.
Lot’s of thanks to the community for providing a alternative choice…
Keep up the good work guys…
ximian says that they aim to have C# in full gear for the 1.0 release (well they claim it’s already production-ready…months ago!) and VB.NET will be for a post-1.0 release (1.1? 1.2? forgot). right now VB.NET is working partially, and they got a huge boost from a commercial developer that donated their VB runtime implementation in Java (so now they’re converting it to C#)
subject says it all
While MacOS packages have not been posted yet, they will be soon. Beta 2 will have official MacOS support. It works really well today and you can build from source. Look at the release notes.
I think it is cool and will probably boost application development on Linux.
This could be one of the most significant achievements in OSS since the Linux kernel itself.
Do these guys r0x0r or what?
Have not heard of any *BSD support yet. Does anyone have that working?
mono doesnt perform very well in freebsd
Yeah, it works on FreeBSD, never saw any reason to try it out yet thought.
what about NetBSD
pkgsrc package is located at:
ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/lang/mono/
Regards
Andreas
BlackCat wrote:
> Coding with it is once again a rush I haven’t felt since I
> first found Python. I for one will not be programming
> GNOME/GTK desktop applications in C for the rest of my life,
> [snip]
Ahh,.. I recommend the TOAD C++ GUI toolkit.
http://www.mark13.org/toad/
🙂
BlackCat wrote:
> Coding with it is once again a rush I haven’t felt since I
> first found Python. I for one will not be programming
> GNOME/GTK desktop applications in C for the rest of my life,
> [snip]
Ahh,.. I recommend the TOAD C++ GUI toolkit.
http://www.mark13.org/toad/
🙂
The fact that this toolkit buys you some interoperability with Windows is a nice side effect, but even if you just want to stay in the linux world, Mono is rapidly becoming the tool of choice. C# is being gradually accepted as a useful application language. Gtk# and other bindings are making it simple to hook into the UI. The runtime has excellent performance.
What else compares? The JDK compares but Swing has never taken off. Its just too ugly. How many Swing apps do you use? Exactly.
A nice IDE with a forms designer similar to the way Delphi or Sharp Develop works.
I have looked at mono develop, but they don’t seem to interested in adding a GTK# form designer.
How is the drawing handled on windows? Via links to libgdiplus from MS or are they using Cairo?
I only hope that they choose a standard gui framework. if not gtk#, something like the Windows.Form that will work like wxwindow.
Mono can become the standard multiplatform developpement framework, but imagine if it loose the .net avantage to incorporate everything in the
runtime and start a dependencies hell.
Windows “typical(not tech)” users already have probleme to install java and to deal with it interface.
Imagine now that mono programs need a bunch of other tools to be installed for every program that need to be run.
It would look unfinish and unprofessional.
So people would develop in .net, then there apps will be cross platforme and forget the mono inconsistency.
[quote]How is the drawing handled on windows? Via links to libgdiplus from MS or are they using Cairo?[/quote]
As far as I know, they call GDI+ directly. Like, ah, System.Drawing–>libgdiplus–>cairo is just how they do things on Linux/the *nixs and the BSDs.
@sanctus: It would be wise to steal Microsoft’s ClickOnce technology: http://www.windowsforms.net/WhidbeyFeatures/default.aspx?PageID=2&I…
That would handle the issues of dependencies automagically on Linux (Windows, perhaps, if they wanted to), you know, that’d make it a real shining diamond for developers to know they could invoke automagically download of dependencies!
People who complain that Mono will always be playing second fiddle to Microsoft’s implementation need to be beaten around the head with this picture:
People who complain that Mono will always be playing second fiddle to Microsoft’s implementation need to be beaten around the head with this picture:
http://primates.ximian.com/~miguel/tmp/two-stacks.png
Of course, by the time they get Mono 1.0 out the door, you’ll probably see VS 2005 out with Windows Forms 2.0 and the whole 9 yards, so that leads me to believe that Mono will be compatible with this generation of .NET when the next generation has been released.
“Just to be completely clear though, my understanding is that Mono is GPL, but is it entirely so? Is it really completely free from MS licensing and such? Is it just the Mono runtime and Mono libraries, or is the MS compatability GPL too?
”
mono is a mix of mit and gpl licenses but regardless of the license if MS has a license it can enforce it. patents have nothing to do with a license thou the intellectual world likes to call it “intellectual property”
clear?
Of course, by the time they get Mono 1.0 out the door, you’ll probably see VS 2005 out with Windows Forms 2.0 and the whole 9 yards, so that leads me to believe that Mono will be compatible with this generation of .NET when the next generation has been released.
Uhmm, Mono 1.0 is scheduled to come out on June 30th.
Uhmm, Mono 1.0 is scheduled to come out on June 30th
Alright then, I stand corrected
If it’s got good support for Windows Forms, I’ll probably port any desktop apps I write in .NET that’ll cross over without too much teeth pulling.
“Alright then, I stand corrected
If it’s got good support for Windows Forms, I’ll probably port any desktop apps I write in .NET that’ll cross over without too much teeth pulling.”
windows forms is called so because its pretty much tied to the underlying platform. windows forms support is going to be unstable in mono 1.0. if you want cross platform compatibility with .net using mono your best bet is gtk#. they use native widgets are better supported
read
http://www.go-mono.com/winforms.html
“Alright then, I stand corrected
If it’s got good support for Windows Forms, I’ll probably port any desktop apps I write in .NET that’ll cross over without too much teeth pulling.”
Hey, brother! You may want to use Portable.NET if you’re heavy on the Winforms and nothing else (100% managed) – they have a much better windows.forms implementation that Mono, sadly. Theirs is very much usable right now, except for the rich text components, but those are always a pain to implement, you know?
Mono is trying to take the noble path with Wine, but it doesn’t exactly work “out of the box” like Portable.net’s windows forms.
…is to emphasize their open source class frameworks instead of pushing compatibility with MS .NET framework classes (where they WILL always be playing second fiddle and catching up all the time).
then get some user-friendly development tools to exploit that API stack. wow. they might end up subverting java on the desktop (and relegate java/j2ee to the server)
Someone should do a writeup that addresses how to get dotGNU winforms running on mono. Now that theming support is supposedly in there, it should be interesting to see how it runs on mono.
i think that eventually we shouldn’t let system.windows.forms use flourish in linux/unix just because it can be done. we should instead encourage development using cross platform classes like GTK#. windows forms should just be there to ease porting of C# windows programs.
Mono can run DotGNU’s SWF implementation. Also, Mono’s own SWF is going to be delivered at the end of the year and has full API support