Thoughts on Mono?
-
:laugh: Yeah, to be followed by "Surround" in version 4.0 or 5.0 depending on the speakers features. :-):rolleyes: In case you didn't know, it's actually named after the word "monkey" in Spanish. Regards, Alvaro
Give a man a fish, he owes you one fish. Teach a man to fish, you give up your monopoly on fisheries.
5.1 required for DTS. :rolleyes: -- Ich bin Joachim von Hassel, und ich bin Pilot der Bundeswehr. Welle: Erdball - F104-G Starfighter
-
Days after the Mono 1 release, Mono dev lead Miguel de Icaza decided on rewriting the System.Windows.Forms implementation for Mono. His post regarding this is here. #include "witty_sig.h"
Finally! I couldn't understand why they had to use wine to begin with. It's basically a large chunk of windows - and they'd use that to just do windowing and/or graphics!? Overkill if you ask me. -- Ich bin Joachim von Hassel, und ich bin Pilot der Bundeswehr. Welle: Erdball - F104-G Starfighter
-
Finally! I couldn't understand why they had to use wine to begin with. It's basically a large chunk of windows - and they'd use that to just do windowing and/or graphics!? Overkill if you ask me. -- Ich bin Joachim von Hassel, und ich bin Pilot der Bundeswehr. Welle: Erdball - F104-G Starfighter
-
Sleep has been deprecated. ;P Jeremy Falcon
Not deprecated - the Mono team just could get that into their BCL either! ;P
Microsoft MVP, Visual C# My Articles
-
Finally! I couldn't understand why they had to use wine to begin with. It's basically a large chunk of windows - and they'd use that to just do windowing and/or graphics!? Overkill if you ask me. -- Ich bin Joachim von Hassel, und ich bin Pilot der Bundeswehr. Welle: Erdball - F104-G Starfighter
If they left the Microsoft System.Windows.Forms in tact, they would have to. Almost every control in Windows Forms (and many classes throughout the BCL) encapsulates native APIs. The Windows API and Common Controls are used heavily throughout Windows Forms (just look at all that's done via a
WndProcoverride, which represents the WindowProc), so building Windows Forms on top of Wine lets them get away with minimal changes to the Microsoft assemblies, if any are even needed. The less they have to do, the better (both in the short- and long-terms).Microsoft MVP, Visual C# My Articles
-
Now Mono 1.0 has been released, whats everyones Thoughts on Mono?? In the brief time I have been playing with it I have got it to run 2 Visual Studio 2003 compiled VB.NET Console applications. Havnt tried ASP.Net yet. It had problems running the WinForm's Application I wrote mind you. Next thing to try is the Console App's on Linux :-) It does also mean, that any products I write in Visual Studio on a Windows box will (can) be cross-platform. Anyone know of any linux Web Hosts that are looking to implement Mono? If this takes off it could lead to very cheap "Microsoft .Net Compatiable" Hosting.. John Crocker
John Crocker wrote: Thoughts on Mono? Don't know why this just popped into my head: Mono is Spanish for Monkey. I don't know if it means anything - Just a random stray thought on "mono".
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell The Second EuroCPian Event will be in Brussels on the 4th of September Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way!
-
John Crocker wrote: Thoughts on Mono? Don't know why this just popped into my head: Mono is Spanish for Monkey. I don't know if it means anything - Just a random stray thought on "mono".
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell The Second EuroCPian Event will be in Brussels on the 4th of September Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way!
Yep, which is why the Mono logo is a monkey. :) #include "witty_sig.h"
-
Yep, which is why the Mono logo is a monkey. :) #include "witty_sig.h"
Judah Himango wrote: which is why the Mono logo is a monkey :doh: Maybe I should just go and find out more about Mono...
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell The Second EuroCPian Event will be in Brussels on the 4th of September Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way!
-
John Crocker wrote: It does also mean, that any products I write in Visual Studio on a Windows box will (can) be cross-platform. No, it doesn't. If you use for instance PInvoke, it won't run on Mono. I am pleasantly surprised they made 1.0. However, I still think it is too risky to use Mono for production code. Heck, I avoid even Microsoft .NET for critical pieces of code - I stick with ISO C++ for that. Maybe in 5 years, though...
Nemanja Trifunovic wrote: No, it doesn't. If you use for instance PInvoke, it won't run on Mono. It has nothing to do with P/Invoke. Mono use WINE on linux for SWF support (and from what I hear its just stable enough for a screenshot). P/Invoke is a core part of the CLR, I very much doubt they would not have that! top secret xacc-ide 0.0.1
-
If they left the Microsoft System.Windows.Forms in tact, they would have to. Almost every control in Windows Forms (and many classes throughout the BCL) encapsulates native APIs. The Windows API and Common Controls are used heavily throughout Windows Forms (just look at all that's done via a
WndProcoverride, which represents the WindowProc), so building Windows Forms on top of Wine lets them get away with minimal changes to the Microsoft assemblies, if any are even needed. The less they have to do, the better (both in the short- and long-terms).Microsoft MVP, Visual C# My Articles
Heath Stewart wrote: The less they have to do, the better (both in the short- and long-terms). The problem I heard is the WINE API changes every week :p top secret xacc-ide 0.0.1
-
John Crocker wrote: It does also mean, that any products I write in Visual Studio on a Windows box will (can) be cross-platform. No, it doesn't. If you use for instance PInvoke, it won't run on Mono. I am pleasantly surprised they made 1.0. However, I still think it is too risky to use Mono for production code. Heck, I avoid even Microsoft .NET for critical pieces of code - I stick with ISO C++ for that. Maybe in 5 years, though...
Wrong. Mono uses Wine for PInvoke support (but WinForms is not part of the 1.0 release). Tomaz
-
John Crocker wrote: It does also mean, that any products I write in Visual Studio on a Windows box will (can) be cross-platform. No, it doesn't. If you use for instance PInvoke, it won't run on Mono. I am pleasantly surprised they made 1.0. However, I still think it is too risky to use Mono for production code. Heck, I avoid even Microsoft .NET for critical pieces of code - I stick with ISO C++ for that. Maybe in 5 years, though...
Nemanja: Code that uses PInvoke will work on mono. As long as you link to a library that exports the function you are calling. This is similar to any other language. For example, if you use JNI you must ensure that the native code you are calling is provided on all platforms you want to run on. Similarly with C++ as well :-) -- Cyrus (http://blogs.msdn.com/cyrusn)
-
Heath Stewart wrote: The less they have to do, the better (both in the short- and long-terms). The problem I heard is the WINE API changes every week :p top secret xacc-ide 0.0.1
Mhmm.. A wine is supposed to mature before enjoyed. :) -- Ich bin Joachim von Hassel, und ich bin Pilot der Bundeswehr. Welle: Erdball - F104-G Starfighter