Slashdot Mirror
Mono 2.0 and .NET On Linux
Several readers noted the release of Mono 2.0, which is compatible with Microsoft's .NET Framework 2.0. According to Miguel de Icaza, "... users can move over server applications built for .NET and client applications built with Windows Forms." InternetNews points out that only about half of the .NET apps out there will work on Mono 2.0, for a variety of reasons including (but not limited to) legacy Windows-only libraries and Microsoft's progress on .NET 3.0 and 3.5 APIs.
I don't think it should surprise anybody that Mono 2.0 cannot handle applications written for .Net 3.0 or 3.5...
I like Mono, I really do, however it's always playing catch-up, it's by it's very nature it's always going to be one step behind Microsoft. Without the support of features in .Net 3.5, very few people are going to choose it for new developments.
If we wanted to run crappy Microsoft technologies, we'd just go buy Windows, wouldn't we?
That must be why the WINE project is such a silly idea... oh wait...
Most of it anyway; but crucially, LINQ.
The bits missing (Windows Workflow Foundation, Windows Communication Foundation and Windows Presentation Foundation) aren't as crucial in my personal opinion; they are just nice toys you aren't going to miss if you've never had them before.
LINQ however is a killer feature IMO; I'm glad to see that's now available on mono.
throw new NoSignatureException();
"A question: Is there a functional IDE for Mono, for us who don't want gnome or even gnome libs on our System?"
Um, what? You'll get gnome cooties?
Monodevelop is a good IDE, and I don't think having GTK and related libs installed is going to steal your masculinity or anything.
Trust the Computer. The Computer is your friend.
Except that C# is a decent little language? It's good to see it open-source, that way it can have a life after Microsoft tires of it.
I don't want to run my stuff on Microsoft technologies but I have potential (and actual) customers who already do use them.
In order to integrate their application and ours we needed to code a little plugin to run on their ASP.NET (or whatever the correct name is) servers.
Mono allowed me to develop the required plugin on a Ubuntu box. (They then wanted the resulting assembly signed, we gave them the source code so they could do it themselves).
Microsoft was relevant to us because we had a potential customer who used it and isn't about to abandon their entire existing system just for us.
Without Mono there would have been two options: .NET
a) Pony up to MS to develop in
b) Don't do the business.
neither of which are particularly appealing.
Mono allows competition and competition is good.
Boffoonery - downloadable Comedy Benefit for Bletchley Park
Yeah, it's a bitch trying to develop .net apps on my Amiga. I wish developers would stop assuming I'm using a Linux distro with features. Assholes.
How we know is more important than what we know.
Good luck porting over LoadDLL("C:\\windows\\system32\\mylib.dll");.
The existence of a working mono is a necessary condition, not a sufficient one, for porting an application. Whether that condition is fulfilled and to what degree, I'll leave up to you to discuss.
Portability comes from being largely independent of the differences between the platform you want to port from and the one you want to port to. Good portability engineering consists of gathering all the platform-specific bits into one unit with a uniform interface, such that it's easy to write platform-specific modules for all the platforms you want to support; then, make sure to test on all your target platforms.
For a good piece of engineering, see Simon Tatham's puzzle collection (http://www.chiark.greenend.org.uk/~sgtatham/puzzles/). To see the importance of testing on all your target platforms, see the state of synergy on the Mac (http://synergy2.sourceforge.net/ -- "The Mac OS X port is incomplete [...]"). To see the importance of isolating your platform dependence, see any code that makes liberal use of fork and ioctl everywhere [sorry, I can't name an example].
Also, good portability engineering done up front is much less work (i.e. cheaper for your employer) than when the project is already deployed on windows only.
-- Jonas K
I agree. Why don't these people who want to use .NET (managed code) just use Java? At least that is platform agnostic (limited to whatever platforms Java is ported on).
By the way, what about dotGNU? http://www.gnu.org/software/dotgnu/ At least that will be released under GPL and not some dual licence with GPL.
Or we can create something on Linux that has to run on Windows (for whatever reason). This is a two way street - Mono can create software that runs on Linux, Solaris, Mac OS X AND Windows.
This isn't just getting Windows stuff to run on Linux.
Viewed from this perspective it is less important that Mono is behind .NET - if you're creating something new you target Mono and it should run on .NET
For many users Windows is where they are (stuck quite often) and they can't migrate 100% of their desktops to *nix, they have something that stops them on a number of systems. Mono means they can create applications that can run on a mix.
There's a big difference between the two - because devs don't target WINE, WINE is the "embrace" part of moving from Windows. Because devs target .NET, .NET is the "embrace" part of moving from Linux.
So, these two technologies are actually on opposing sides of this particular ideological fence - one is an attempt at removing lock-in, the other is an attempt at locking-in.
I'm a minority race. Save your vitriol for white people.
As a Programmer I am really torn between Java and Mono!
Both platforms solve the same problem but which one shall I commit to?
Do I install and run both platforms on my PC?
Surely running both platforms at the same time *must* be detrimental to my PC's performance (e.g. memory usage and cpu time executing both VMs)!
I also cannot afford the time to learn both platforms properly!
It is unfortunately a question of politics. .net technology and patents are a concern.
Java is now open-sourced and offically sanctioned.
Mono is the "unauthorised"(by Microsoft) port of
Both platforms have great software written for them (e.g. banshee, jedit, monodevelop, eclipse and netbeans) and patents are not really a concern to me because I live in the UK (software patents do not apply...YET!).
It is unfortunate that the mono is so closely associated with Windows, if the mono team had created/implemented a completely new set of cross-platform libraries (that bore no relation to Microsoft's framework) it would be more accepted.
I really like mono - the work that has been done is nothing short of amazing but the constant catch-up with Microsoft is a concern.
Java is widespread in mobile phones and most modern desktops unfortunatly for me it is not available on my PDA (ipaq 2210).
I am really stuck with this! :(
I wish the real .NET could be installed on Wine. Not because I like .NET, but because I want to run those programs that people make in .NET these days, in Wine just like I can do with regular programs. If Wine wants to work like Windows, it should also be possible to install the real .NET on it just like you can do on the real Windows. They should try to make it work just as well as they did with MS Office. Then it would become possible to run so much more programs in Wine without problems and without having to reboot to Windows!
The only .NET apps I use are nLite and vLite. The fact that these both launch native apps means that perhaps the interfaces (which are AFAIK Windows.Forms) will load but they will not be able to be front-ends to their Windows native apps that they are launch. This is very unfortunate and I wish Wine and Mono could work together to solve this problem. A lot of .NET apps launch non-.NET apps. They should at least make an #ifdef __WINE__ or something to allow the Exec() command or whatever it is to replace the command with a Unix command like wine . Most things will probably work okay.
Patent encumbered lock-in of future software?
I'm a minority race. Save your vitriol for white people.
You're not making much sense. Yes, people don't target WINE, they target the Windows API, just like they target the .NET API. Wine is a means of running Windows code on linux, Mono is a means of running .NET code on linux. People will be writing code for both, so might as well support running it on linux.
Mono is Java in disguise, if you want cross platforms without traps use Java
It is like the mortgage crash, a few saw it coming, they said so, but the majority didn't care
A few people says that Mono is a legal and technology trap (search the web for mono trap), in the future this will reveal true, do not forget that you where warned
The .NET platform and C# looks like decent enough technology, but I just don't think it's compelling enough to prompt a switch from Java.
With these back-room Novell/MS deals, the patent situation around Mono continues to be as clear as mud, and with Java I get it all under the GPL (with a clear and written patent grant) right from the source. Not to mention Sun's process for advancing the platform (JCP), while not perfect, is far more open and community driven, catering to much wider variety of vendors and platforms than Microsoft.
With Eclipse and Netbeans, the Java tool support on Linux is fantastic as well. With RedHat and JBoss, the server platform is also well supported on Linux.
So, yeah, nice work, but no thanks.
*sigh*
.NET provides it. WINE helps people leave windows and still keep their legacy applications. Mono provides a way for new applications to be moved from Linux to Windows.
.NET that can be run on Mono, in which case we have bigger problems, such as lack of intellectual integrity on the part of those making the argument
WINE removes lock-in,
Unless, of course, the argument is made that there are legacy applications in
I'm a minority race. Save your vitriol for white people.
I'm guessing that 40% of those incompatible apps are due to code which references Win32 libraries via P/Invoke. Seriously, almost no-one is developing for .NET 3.x. Most apps are written for 2.0, which is included with XP SP2 and Vista, but 3.5 is a 300MB download, so almost no-one has it. Microsoft had to release a client-only subset version of it which is cut down, and its around 30 MB, but it'll cause a lot of confusion (RE: versioning), and I don't think it supports LINQ.
Most human behaviour can be explained in terms of identity.
"InternetNews points out that only about half of the .NET apps out there will work on Mono 2.0"
On my Windows XP computer half the .NET applications break anyway.
-Woof woof woof!
the portability is a myth. look at how much applications are written in a portable way (OpenOffice, for example)
posix and c/c++ where portable and uniform across operating system for at least three decades, and if cross platform development doesn't thrive on those, then none of those wannabe portable languages will do any good for portability.
portability using a common runtime is a myth, and is a weird version of the microsoft format lockin (yes applies to Java too). look at how many platform debian packages are compiled towards, THAT is portability.
Before I tear apart what you think passes for an argument, let me say that the Mono folks are doing an amazing job and they get way too little credit. The tinfoil hat brigade around here seems to have taken on Mono as its personal whipping boy, and it's totally unfair and uncalled for.
Sure, but weren't you supposed to be talking about Mono there somewhere? Java used to provide lock-in, too. Hence, the GNU Classpath project, which is pretty much identical in its goals to Mono. Funny that I never saw you people screaming about that one being a trap.
Wow, get some perspective there. How many killer apps are there on Linux that the Windows people are craving? KDE? Gnome? Firefox? OpenOffice? None of those are on .NET and most of them run on Windows, anyway. Do you think that Firefox, OOo and KDE are all helping people move away from Linux by providing Windows ports? Isn't it more likely that without those Windows ports, most of these projects would go nowhere?
It's really quite obvious to anyone with any actual knowledge of how the industry works that people are going to write applications without Linux in mind. The Mono project, just like the Wine project, lets people who run Linux run applications that other people wrote for Windows.
As it turns out, there's also a bunch of useful libraries that Mono includes that you can use when coding for platforms other than Windows. It boggles my mind that anyone would think that this is somehow a trap. It's just a useful way to access Unixy things on Mono. But it clearly can't be breaking Linux lock-in or whatever pea-brained scheme you've come up with.
.NET has been around for 7-8 years now. Do you honestly think code can't become legacy in that amount of time? Here's a tip: if you think Linux has any lock-in potential for applications written on it, then perhaps you shouldn't talk too much about intellectual integrity.
Wine makes it possible to run Windows applications, built on the WIN32 API, to run on Linux. Mono makes it possible to run Windows applications, built on the .NET framework, to run on Linux.
In both cases, most applications will probably be developed primarily for Windows, but can also be run on Linux. Yes, you can develop .NET apps on Linux, run them on Linux and then move to Windows while keeping your .NET apps. That doesn't mean that Mono provides lock-in. It just means that .NET/Mono comes closer to cross-platform portability than WIN32/Wine does...
I for one look forward to games coming out using .net and managed opengl libs. Suddenly game makers won't have to do much work at all to write games that perform well on windows, linux, even osx. Sounds like removing lock-in to me
I think the mono project was started primarily because of interest in the C# language, as it compares favorably to java, fixing many of Java's flaws.
Sadly while the C# language may be in many ways stronger than Java, the platform is much weaker. Realistically, the reason Java was so successful was that there were high quality VM and classpath implementations on all platforms. Yet, Microsoft didn't seem to learn this lesson from Java, and instead relied on third parties, who can't possibly maintain parity with Microsoft .NET. Thus, .NET will always be a second class citizen on Linux, and always a poor choice compared to Java.
As much as I like C#, it's a foolish choice to write Linux apps in .NET in the same way that it is foolish to write them in win32. It will always be a second rate platform on Linux, so long as the people controlling the standard have no interest in doing the work to making the framework work across platforms.
really? I thought MS has dropped support for OpenGL, apart from its very legacy v1.1 base. And you know they will never write a managed wrapper for it.
So, who will write a .NET game using opengl? If you're a Windows dev (and most game devs are) then you'll be using DirectX.NET, which oh so conveniently is not available for Linux.
So close. Yet so immensely far. Do you see the problem now? Its business a usual for MS, but with the added bonus of saying "But we are working on Linux interoperability, Mr DoJ, look - Mono".
well, it snot that decent a little language. Its a MS port of Java with extra bits added mainly in the realm of the GUI and interop with legacy COM and Win32.
They have added extra features that are cool, like LINQ, but I feel they'll be heavily misused over the coming years. They've also adding features like extension functions which will make scripting languages look like statically strong-typed languages compared to C# as time goes by.
Its also pretty complex for a little language, I'm seeing a lot of people complaining on the web about how they're using up all their memory followed by little tutorials on Dispose and releasing objects so they actually get disconnected and then freed by the GC.
I think if it wasn't for curly braces, and the .NET class library, hardly anyone would be using it. Imagine if MS only released VB.NET, you wouldn't use it, the classic VB crowd wouldn't use it, but its practically the same language as C#.
BTW. C#2 is a standard, C#3 is not. MS has promised to submit it, but they havn't yet.
To be pedantic I think the C# language definition is open source. What isn't is the runtime. You could write a C# compiler with its own runtime and you'd have a pretty nifty alternative to Java.
What you can't do is copy the windows runtime. I wonder how mono would do if Microsoft invoked patents against it. I suspect not well, but with Mono in its current state it is to MS's advantage - they can say they are multi-platform but know that most people will give up because of the 50% of programs that won't run and turn to Windows.
FLAMEBAIT -- get a life! Anyone who has experience of both J2EE and .NET will tell you that .NET is better thought out, has a more consistant design,
has cleaner easier to use APIs, scales better, performs better
and is altogether a much nicer environment to work in.
I am sorry if this upsets the Slashdot worldview but its the truth. Microsfot are better at software than Sun.
Anyone who has experience of both Apache and IIS will tell you that IIS is better thought out, has a more consistant design, has cleaner easier to use APIs, scales better, performs better and is altogether a much nicer environment to work in.
I am sorry if this upsets the Slashdot worldview but its the truth. Microsfot are better at software than FLOSS Devs.
Because, we all know that those are the only things that matter when gambling your future - your legal liability is irrelevant.
I'm a minority race. Save your vitriol for white people.
WINE is as to Windows as Mono is as to .NET
This is basic logical reasoning.
If you think MS doesn't have patents on parts of the Win32 API, then you're really messed up. The cross-patent licensing deal with Novell was for all patents. It would also include any Win32 patents. NET vs. Wine isn't relevant there since the patents involved weren't divulged..
.NET apps to run on Linux. People now write for Mono. Wine started as a way to compile Windows Apps for use on Unix. People now also write and certify their applications for Wine. You also appear to think this is different, and somehow get people to mod you up for your poor reasoning.
Mono started as a way for
Put identity in the browser.
Anyone writing for Gnome should use Vala, Gnome's own c#-alike language.
Put identity in the browser.
It's too bad that its primarily for Linux and other platforms have varying levels of support. Considering Mono is supposed to be a cross-platform runtime, it doesn't instil much confidence that an IDE written in .NET expressly for Mono development can't even run everywhere. SharpDevelop (which MonoDevelop was ported from) isn't much better either. Why is it so hard to make an IDE that runs everywhere?
I'm surprised that more effort isn't going into MonoDevelop. At the moment the defacto .NET development platform is DevStudio. This automatically means that developers develop against Microsoft's runtime, not Monos and also encourages all sorts of bad practice such as DllImports, embedding ActiveX controls, dependencies on other MS tech like SQL Server etc. Perhaps if MonoDevelop were to .NET development what Eclipse is for Java development it would gain a lot more traction. Eclipse manages to be cross-platform. It even runs on different JVMs including (surprisingly gcj). This is where MonoDevelop needs to be.
Anyone writing for Gnome should use Vala, Gnome's own c#-alike language.
Or writing for Maemo. It's a pretty fantastic way of getting lean programs with advanced language features. Unfortunately, it's still a little lacking for bindings in the stable version (GNet wasn't functional in the last stable version, which was a deal breaker for the stuff I was doing.), but it's very promising for embedded apps.
"He may look like an idiot, and talk like an idiot, but don't let that fool you. He really is an idiot." - Duck Soup
Comparing Visual Studio to something like Eclipse isn't exactly a fair comparison, since Visual Studio doesn't do cross platform, at all. For anyone who doesn't live, eat and breathe Microsoft products, this is a bit of a problem. Monodevelop is currently the only almost equivalent for doing .NET work in a cross platform visual way....
That being said, if you're doing heavy duty development work and don't use Windows, Eclipse is a much better environment than Monodevelop, so it's pretty safe to say that Java development on non-Windows systems is easier than .NET development. If you don't use Windows.
"He may look like an idiot, and talk like an idiot, but don't let that fool you. He really is an idiot." - Duck Soup
Sure, but weren't you supposed to be talking about Mono there somewhere? Java used to provide lock-in, too. Hence, the GNU Classpath project, which is pretty much identical in its goals to Mono. Funny that I never saw you people screaming about that one being a trap.
WINE allows you to run Win32 applications on X/Unix. Mono allows you to run .NET applications on Linux. While superficially these appear similar, there's an important difference: WINE and classpath implement specifications that are publicly available whereas Mono, through a deal with M$, implements something which is not freely implementable. The difference shows up like this: you can write an alternative for classpath or for WINE (although it would take another 10 years) but you can't write an alternative to Mono (no matter how many years you take) without having a deal with M$ either directly or indirectly. In summary, M$ CONTROLS who can implement .NET while that is not the case with Win32 or Java. Can you see the Lock-In now? Anything that requires you to have a deal in order to implement it is not an open standard.
The largest prime factor of my UID is 263267.
As a .net developer, you have to notice that Managed DirectX doesn't exist anymore, and XNA is too nowhere near as powerful as MDX was. There is SlimDX, which is a binding around DX10, which is quite cool, but has only become available recently.
.NET. It provides cross platform .NET bindings for openGL, SDL/glut/glfw, as well as OpenAL, devil and CG. It's basically a cross platform XNA equivalent.... but a lot better ;)
/. is full of MS bashing, I'd actually suggest you go try mono with the Tao framework, and it might prove to be a suprisingly pleasing environment to work in....
The Tao Framework is more or less the best thing out there right now for
Whilst i appreciate
C# is an iso standard language, which puts it in the same league as C/C++.....
Before I tear apart what you think passes for an argument,
"Ad hominem"
Erm... do you know what 'ad hominem' means? This is insulting your argument, not you personally. It's insulting to you personally by proxy, on the basis that you believe your argument etc etc. Okay, yes, there is an ad hominem element to it still as you are insulted along with what you said, but that doesn't invalidate it. "Ad hominem" is hardly a defence.
"Then you have a short memory"
Or more likely: hasn't come across posts where you express the bug up your ass about java.
"Wine does, certainly"
Erm... mono "certainly" does too... not *all*, and often without some porting (such as changing paths to reflect unixy filesystems), which is stated. You may remember what WINE was like as 'early' into the project as Mono currently.
Among other things, Mono allows transference of skills of Windows programmers to Linux systems, should they desire to work under Linux. If you think people are going to develop under Mono on Linux, and then move their projects over to the Windows platform instead, I think that demonstrates how little confidence you have in Linux.
"Irrelevant, Ad hominem and a strawman. Well Done!!!"
Untrue, irrelevant, untrue, and unduely patronising.
The revolution will not be televised... but it will have a page on Wikipedia
All the budding developers who hear about .NET's cross-platform nature will want to learn it. All, except the wisest, of them will be forced to learn MS .NET from MSDN. They'll code a few .NET applications in C#, test them on M$ Windows and let their brains embrace .NET beyond all question. One day they find that most of their applications don't work on Linux/Mono. They'll scream on all public forums - "Linux is crap!!!". Someone tries to explain to them that the problem is because of their heavy usage of M$-specific extensions which are not part of ECMA .NET. Then they'll scream again - "ECMA .NET?#??!!#! WTF is that?". Such is the depth of lock-in involved with .NET.
The largest prime factor of my UID is 263267.
Or better: Write a C# compiler that compiles to the java virtual machine.
My claim is that of the two techs mentioned (Wine and .NET), one enables migration from Windows, the other prevents it.
And Mono now negates that last part you said since it allows you to move .NET code over to *nix, so, relating to the actual discussion of Mono, what exactly is your point again?
You may be a master of C#, but you clearly know very little about Java - all objects are passed by reference in Java. Fundamental types like int, long, etc. are passed by value, and I understand this is the same in C#.
You haven't answered the question: Why not use Java...or for that reason, why use .NET for cross-platform development over Java?
There are many IDEs written in Java, and I refuse to run Silverlight/Moonlight on my machine as long as it's a MS proprietary solution (ie: let's-trap-the-customer-into-another-windows-only-solution).
Goodbye Slashdot. You've changed.
C# is an iso standard language, which puts it in the same league as C/C++.....
...and OOXML.
Yes, they will both be in a struggle to maintain 100% compatibility as well, to a point. As soon as Mono comes out with a new version Microsoft will create a new incompatible version like they have been doing. This is the position MS want to be in. They've somewhat lost the ability to change Win32 because it would break everything. They can create a new version of .NET and just claim you need the new run time. Seriously. Why do we need 6 run time environments (1.0, 1.1, 2, 3, 3.5 ... and soon 4)? While I am on the subject... if 3.0 is built on 2 with WPF, why isn't it called 2.5 and why isn't 3.5 (3 with LINQ?) called 2.55? I mean, let's give Java it's due. Version 1.6.4 will run all old Java code and .NET 2 won't run 1.1 byte code without the 1.1 libraries.
Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
Java used to provide lock-in, too. Hence, the GNU Classpath project, which is pretty much identical in its goals to Mono. Funny that I never saw you people screaming about that one being a trap.
The Java Trap was that you might get stuck on a language with no FOSS implementation and be reliant on a proprietary runtime. GNU Classpath and friends disarmed the trap by providing FOSS backends.
The Mono Trap is that you might get stuck on a platform encumbered by patents, so that even if you're coding on a 100% FOSS system, a court ruling granting an injunction against further release and development of Mono could yank the rug out from under you. Maybe that's no big deal for cute games or desktop applets, but there's no way on Earth I'd stake my business on a platform that may be nuked from orbit at any moment.
It's really quite obvious to anyone with any actual knowledge of how the industry works that people are going to write applications without Linux in mind.
It's equally obvious that Microsoft has never entered a relationship without destroying its partner. The naivety behind thinking that maybe they'll play nice this one time, for the first time in the history of their company, is simply astounding.
Dewey, what part of this looks like authorities should be involved?
Warning: Incorrect merging of two geek quotes!
Correct quotes:
Admiral Ackbar(RotJ): "It's a trap!"
Ash (Army of Darkness): "It's a trick. Get an axe."
It's false logic, as demonstrated by the fact that people don't target Wine
Uhh... yeah they do. How do you think Google ported Picassa to Linux?
Thats the exact position Java has been in for years. Language Spec and JVM spec were open, but Sun's runtime was not. Anyone could make their own runtime. Yet people complained that Java was not open. So why would MS get special treatment for an open spec without an open platform?
SharpDevelop is better than Monodevelop, and is BSD licensed. It also, frankly, pwns the crap out of Eclipse. The only reason I don't use it on Windows (its much faster than VS, btw) is that its refactoring tools aren't yet on par with the excellent Resharper add-in.
You missed the most important part, which was the cross platform part of it. SharpDevelop works under Windows, nothing else. Monodevelop is more or less a port of SharpDevelop meant to work with GTK#.
As far as cross platform stuff goes, Monodevelop is all you're left with for C# stuff (if you discount Eclipse plugins).
Regardless, you can compile cross platform binaries with Visual Studio. If your time is worth so little that the $200 license for Windows is too high, then I respectfully suggest you reconsider either your rates, or your career.
You know, the "Linux users only use Linux because they're too cheap for Windows" meme is a little old. It has nothing to do with the license for Windows -- I just find it to be an inferior operating system for both my development tasks and my daily computing tasks. The fact that you naturally assume that I'd rather waste my time either maintaining a completely separate virtual or physical machine simply for the privilege of having a marginally nicer UI for designing apps which are only guaranteed to work as advertised on a single operating system?
As it stands now, I have no trouble using Eclipse as an IDE... I just avoid using C# for anything other than CLI tasks. Saying that anyone who doesn't use what you use is cheap and/or underpaid and/or incompetent is just plain condescending. If not ignorant. Use what you're comfortable with, and don't dog other peoples' choices in operating systems. It's just a single tool, and not worth scrapping my entire workflow and machine installation to accommodate.
"He may look like an idiot, and talk like an idiot, but don't let that fool you. He really is an idiot." - Duck Soup
Given that Mono runs on Windows, what happens if you try running a Win32 version of Mono under WINE?
It works a little bit better than .NET (with winehacks) as far as running GTK# apps and all, but you might as well use native Mono for that. I got .NET 2.0 installed with winehacks and attempted to run nLite and of course, it crashed (a framework crash, not a Wine crash). I tried with Mono 1.3 last time but that was pointless for that. Wine's project plan is to support Win32 Mono as far as I know (especially since it is free software) to run .NET apps.
Some features in C# such as generics can't be implemented as is to run on a standard JVM because the JVM doesn't have the capability to support it. .NET's CLR was designed to support generics at the byte code level. In Java, generics are implemented by the Java compiler that just hides the object casting from the programmer. The result is that the JVM doesn't really know what the types are at run time.
InternetNews points out that only about half of the .NET apps out there will work on Mono 2.0, for a variety of reasons including (but not limited to) legacy Windows-only libraries and Microsoft's progress on .NET 3.0 and 3.5 APIs.
Exactly, which makes it pretty useless, so it's as bad as OOXML in a way, so tell me again why I'd want to bother writing Microsoft-specific software for Linux? No thanks.
Promote true freedom - support standards and interoperability.