Re: [Mono-list] just installed mono, most basic test failed.
> From: mono-list-boun...@lists.ximian.com [mailto:mono-list- > boun...@lists.ximian.com] On Behalf Of David Curylo > > It's not like Java where you can blindly expect your code to run across > platforms. More like Python or Erlang or numerous other languages and > runtimes where most of the code will work across platforms, but some > libraries are platform-specific. Even in java, python, or any other language, you can't just build and test on one platform and blindly expect (without testing) that it will work on another platform - because there exist platform specific variations. For example: If you wrote an https server application, and it ran on windows as a service, it *won't* simply run on linux. Because binding low numbered ports requires root escalation. So you need to be careful to launch your application as root and then make a POSIX call to drop privilege after the port is bound. And if you use a path like "C:\foo\bar" your app will break on a non-windows platform. And even if you do the smart thing using special folder enumeration... "Personal" evaluates to "My Documents" on windows, but evaluates to your home directory on linux/unix. So you have to use *different* special folder enumerations on different platforms, in order to have the same effect. Not to mention differences of supported filesystem characters... Path separator char '/' vs '\' ... Case sensitive filesystems, vs case insensitive... Unicode vs Ascii ... Disallowed characters in windows... Maximum path length in windows that doesn't exist in linux/unix... What else? There are simply TONS of differences that are different on different platforms, regardless of the language you use. It is not realistic, in *any* language, to write and test on one platform and expect it to be functional on another platform without testing. Unless your app is a trivial calculator or similar. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
Hello, everyone. Pardon my interjection; I wanted to note that we (at our company) have fully working code (mono) running on two different operating systems (Windows and Linux), so while it might not be standard, if you write code to fit different operating systems, it is entirely possible to have cross-platform in mono... But as noted earlier, if this was not done from the beginning and things are hardcoded or use OS-specific functions, this will obviously yield issues. Med venlig hilsen / Best Regards René Holmboe Ditlevsen Network Engineer Fra: mono-list-boun...@lists.ximian.com [mailto:mono-list-boun...@lists.ximian.com] På vegne af David Curylo Sendt: 13. maj 2015 13:22 Til: Pierre-François Culand Cc: Mono-list@lists.ximian.com Emne: Re: [Mono-list] just installed mono, most basic test failed. It's not like Java where you can blindly expect your code to run across platforms. More like Python or Erlang or numerous other languages and runtimes where most of the code will work across platforms, but some libraries are platform-specific. WCF's TCP binding isn't going to work in it's current state, so if you're unwilling to choose a cross platform communications library, then it won't be a good fit across platforms. That's more of a WCF issue than a mono issue, and well, WCF doesn't have cross platform in mind. It's _Windows_ Communication Foundation. If you want binary communications and want it to work cross platform and you want it to be more robust than simple sockets, then I would really recommend you use something more like ZeroMQ https://github.com/zeromq/netmq. On May 12, 2015, at 3:33 PM, Pierre-François Culand mailto:p...@culand.ch>> wrote: Mono is not a fully functional and complete .Net Framework virtual machine for Mac... It's a pity... ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
It’s not like Java where you can blindly expect your code to run across platforms. More like Python or Erlang or numerous other languages and runtimes where most of the code will work across platforms, but some libraries are platform-specific. WCF’s TCP binding isn’t going to work in it’s current state, so if you’re unwilling to choose a cross platform communications library, then it won’t be a good fit across platforms. That’s more of a WCF issue than a mono issue, and well, WCF doesn’t have cross platform in mind. It’s _Windows_ Communication Foundation. If you want binary communications and want it to work cross platform and you want it to be more robust than simple sockets, then I would really recommend you use something more like ZeroMQ https://github.com/zeromq/netmq. On May 12, 2015, at 3:33 PM, Pierre-François Culand wrote: > Mono is not a fully functional and complete .Net Framework virtual machine > for Mac... It's a pity... ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
> From: mono-list-boun...@lists.ximian.com [mailto:mono-list- > boun...@lists.ximian.com] On Behalf Of Pierre-François Culand > > Actually I observe Mono is not a fully functional and complete .Net > Framework virtual machine for Mac... It's a pity... Nothing's perfect, but for a guy who says he doesn't want to develop, build, or test on a different platform - just expects the binaries to unconditionally run on different OSes with zero effort - nothing in the world will ever be good enough. Glad it almost worked. I guess. :-/ ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
Hi all, So I installed Yosemite and effectively, the WinForms basic test now works ! I tried to run my WinForms WCF duplex Client and... ...It runs as long as it does not try to communicate (via a net.tcp binding) with the WCF service hosted on my iis server... Then it crashes and I get some mysterious exceptions related to WCF and tcp sockets... So I suppose I am using some of the partly implemented WCF API... :-( Actually I observe Mono is not a fully functional and complete .Net Framework virtual machine for Mac... It's a pity... Thanks all for your help. Pierre-François -Message d'origine- De : Pierre-François Culand [mailto:p...@culand.ch] Envoyé : lundi 11 mai 2015 22:28 À : var...@ntlworld.com Objet : Re: [Mono-list] just installed mono, most basic test failed. You are right. As I wrote in my first message, the Mac on which I ran the basic test runs IOS 10.6.8 (snow leopard) ! Thank you for your information. I will upgrade to Yosemite and perform the tests again. Envoyé de mon iPhone Pierre-Francois. > Le 11 mai 2015 à 22:27, Pierre-François Culand a écrit : > > You are right. As I wrote in my first message, the Mac on which I ran the > basic test runs IOS 10.6.8 (snow leopard) ! > Thank you for your information. I will upgrade to Yosemite and perform the > tests again. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
Just as a comment, we have been using mono for the past 8 years and our app is very well spilt between client(gui) and backend server with all the client build on windows only and all the backend server compiled on windows and mono on Linux and we have about 3 to 4 million lines of back end code with over 2 test all running on both windows and Linux and 99% of it without change. there are a few areas that are platform specific that need to be addressed but for the most part everything compiles and running and runs on Linux and windows without change. The key is to have a solid split between client(gui) and backend server since the gui is something that you would have thats specific to the platform you are working on, either be it be windows, Linux,ios,android and the server can be designed to be cross platform and communicate between the client and the server through remoting which for the most part crosses between the windows and Linux/mono world with little problem although wcf could also be used . Like a said we are almost 4 million lines of code into it and so far its been working but you have to think about this right at start and cant look at it down the road in the project. Just an observation anyhow. thanks scott -- View this message in context: http://mono.1490590.n4.nabble.com/just-installed-mono-most-basic-test-failed-tp4665880p4665913.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
That is interesting, I suppose if its a console application that you could use vscode and it would compile under Linux -- although I have not gotten it to work at all under Linux, so its in early stages. Edward Ned Harvey (mono) wrote: > > From: cov...@ccs.covici.com [mailto:cov...@ccs.covici.com] > > > > Why not use vs 2015 and vs code, supposed to work on Windows, OSX or > > Linux, although I don't know what versions of OSX they are supporting. > > I wonder how long mono is for this world? > > Is that just a blatant troll? Even with .Net being open source, you cannot > ever expect it to simply compile straight up, on a non-windows platform. Lots > of changes are required under the hood to implement things like file and > socket operations, which are fundamentally based on different underlying > technologies. You should not expect such an effort to ever be done - because > it's already been done in mono, and there's no motivation for anyone to > repeat all that work in a separate project. > > So the long and short of it is: You should expect mono to adopt the .Net > source code rapidly, and therefore mono is and will continue to be > indefinitely, the canonical way of running .Net code on non-windows platforms. > > It just so happens, VS is better than XS/MD in a lot of ways... But XS/MD is > also better than VS in a few ways. Particularly, I don't think you should > ever expect VS to build a Xam.Mac project, and in VS, if you want interactive > code analysis you have to pay for Resharper. But that capability is built-in > to XS/MD. > > Personally I like to edit code in both XS/MD, and VS, so I can take advantage > of the strengths of each. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
Hi Edward, all, On 11/05/2015 15:51, Edward Ned Harvey (mono) wrote: >> From: cov...@ccs.covici.com [mailto:cov...@ccs.covici.com] >> >> Why not use vs 2015 and vs code, supposed to work on Windows, OSX or >> Linux, although I don't know what versions of OSX they are supporting. >> I wonder how long mono is for this world? > Is that just a blatant troll? Even with .Net being open source, you cannot > ever expect it to simply compile straight up, on a non-windows platform. Lots > of changes are required under the hood to implement things like file and > socket operations, which are fundamentally based on different underlying > technologies. You should not expect such an effort to ever be done - because > it's already been done in mono, and there's no motivation for anyone to > repeat all that work in a separate project. > Putting to one side the criticism of Mono, I was looking at some CoreCLR info the other day and it does look like build on Linux is well on the way? It also looks as though they plan to have ARM support in there at some point? https://github.com/dotnet/coreclr/wiki/Developer-Guide Cheers, Alex ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
> From: cov...@ccs.covici.com [mailto:cov...@ccs.covici.com] > > Why not use vs 2015 and vs code, supposed to work on Windows, OSX or > Linux, although I don't know what versions of OSX they are supporting. > I wonder how long mono is for this world? Is that just a blatant troll? Even with .Net being open source, you cannot ever expect it to simply compile straight up, on a non-windows platform. Lots of changes are required under the hood to implement things like file and socket operations, which are fundamentally based on different underlying technologies. You should not expect such an effort to ever be done - because it's already been done in mono, and there's no motivation for anyone to repeat all that work in a separate project. So the long and short of it is: You should expect mono to adopt the .Net source code rapidly, and therefore mono is and will continue to be indefinitely, the canonical way of running .Net code on non-windows platforms. It just so happens, VS is better than XS/MD in a lot of ways... But XS/MD is also better than VS in a few ways. Particularly, I don't think you should ever expect VS to build a Xam.Mac project, and in VS, if you want interactive code analysis you have to pay for Resharper. But that capability is built-in to XS/MD. Personally I like to edit code in both XS/MD, and VS, so I can take advantage of the strengths of each. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
On 20150511 14:30 , cov...@ccs.covici.com wrote: Why not use vs 2015 and vs code, supposed to work on Windows, OSX or Linux, although I don't know what versions of OSX they are supporting. VS2015 is Visual Studio, bunch of code in c++ and still using COM technology, so this will not be ported to anything different from Windows soon. VS team cannot solve 256 length paths and VS is still 64b app (there are some 64b parts talking to 32b VS). VS Code is editor based on Atom (git atom core) and it runs on Ubuntu and Fedora (presonally tested, currently preparing tests on SuSE). If you watch //BUILD talk about ASP.net (Hanselman) you'll notice that there are no plans to make new Visual Studio on Mac and Linux. VS Code is merely editor based on javascript talking to server (omnisharp) to get intellisense and autocompletion + few integrations with system to enable commandline commands and debugging. I wonder how long mono is for this world? Mono is here since 2001 and will stay for some time for sure... thanks regards Mel Edward Ned Harvey (mono) wrote: From: Pierre-François Culand [mailto:p...@culand.ch] I do not intend to develop nor compile my app on the Mac/mono. I just want to deploy and run the already compiled WCF Winforms client .exe app with its WCF config file to consume the WCF service. Oh, you should give up now. There is no chance of simply taking a complex app already built and developed in VS/Windows, and then straight up launching it under mono on a different platform and expecting it to work. Also if you check the mono compatibility page, it says "limited WCF" which may or may not affect you. I don't know if "limited WCF" compatibility affects server-side, client-side, or both. In reality, if you want to develop cross-platform, you can achieve > 95% code reuse, and binary compatibility across platforms, but it's not going to happen automatically except for trivial apps or libraries. You have to develop and test with that goal in mind. You need VS on windows, and XS/MD on mac and/or linux. And you need to test on every platform that you care about supporting. There *will* be differences in the OS, as well as differences between .Net and mono, which you'll have to workaround. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
Thanks for your encouragements ! ;-) Actually, that's exactly what I intended to do when I installed Mono: 1) test my mono installation with basic apps. 2) test running my complex WCF/Winforms client app to see what the "partial WCF implementation" means. But since the basic HelloWinForms app did not run I thought something was wrong in my Mono framework installation... That's what I want to understand first. Why did the trivial HelloWinForms.exe not run without raising a lot of dll not found exceptions !? Envoyé de mon iPhone Pierre-Francois. Le 11 mai 2015 à 13:47, Edward Ned Harvey (mono) a écrit : >> Oh, you should give up now. There is no chance of simply taking a complex >> app already built and developed in VS/Windows, and then straight up >> launching it under mono on a different platform and expecting it to work. > > To REALLY get to the bottom line, just do this: > > You have installed the MDK on a mac. Now copy all your app's exe and dll > files (and any other necessary files) to some directory on your mac, and > simply launch: >mono yourapp.exe > > If it runs, kudos to you. You either have a trivial app, or you've disproven > what I said above. > > If it doesn't run, then there's no escaping the fact, that additional testing > & development would be necessary to make it run. > ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
Why not use vs 2015 and vs code, supposed to work on Windows, OSX or Linux, although I don't know what versions of OSX they are supporting. I wonder how long mono is for this world? Edward Ned Harvey (mono) wrote: > > From: Pierre-François Culand [mailto:p...@culand.ch] > > > > I do not intend to develop nor compile my app on the Mac/mono. I just want > > to deploy and run the already compiled WCF Winforms client .exe app with > > its WCF config file to consume the WCF service. > > Oh, you should give up now. There is no chance of simply taking a complex app > already built and developed in VS/Windows, and then straight up launching it > under mono on a different platform and expecting it to work. Also if you > check the mono compatibility page, it says "limited WCF" which may or may not > affect you. I don't know if "limited WCF" compatibility affects server-side, > client-side, or both. > > In reality, if you want to develop cross-platform, you can achieve > 95% code > reuse, and binary compatibility across platforms, but it's not going to > happen automatically except for trivial apps or libraries. You have to > develop and test with that goal in mind. You need VS on windows, and XS/MD on > mac and/or linux. And you need to test on every platform that you care about > supporting. There *will* be differences in the OS, as well as differences > between .Net and mono, which you'll have to workaround. > ___ > Mono-list maillist - Mono-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-list -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
> Oh, you should give up now. There is no chance of simply taking a complex > app already built and developed in VS/Windows, and then straight up > launching it under mono on a different platform and expecting it to work. To REALLY get to the bottom line, just do this: You have installed the MDK on a mac. Now copy all your app's exe and dll files (and any other necessary files) to some directory on your mac, and simply launch: mono yourapp.exe If it runs, kudos to you. You either have a trivial app, or you've disproven what I said above. If it doesn't run, then there's no escaping the fact, that additional testing & development would be necessary to make it run. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
> From: Pierre-François Culand [mailto:p...@culand.ch] > > I do not intend to develop nor compile my app on the Mac/mono. I just want > to deploy and run the already compiled WCF Winforms client .exe app with > its WCF config file to consume the WCF service. Oh, you should give up now. There is no chance of simply taking a complex app already built and developed in VS/Windows, and then straight up launching it under mono on a different platform and expecting it to work. Also if you check the mono compatibility page, it says "limited WCF" which may or may not affect you. I don't know if "limited WCF" compatibility affects server-side, client-side, or both. In reality, if you want to develop cross-platform, you can achieve > 95% code reuse, and binary compatibility across platforms, but it's not going to happen automatically except for trivial apps or libraries. You have to develop and test with that goal in mind. You need VS on windows, and XS/MD on mac and/or linux. And you need to test on every platform that you care about supporting. There *will* be differences in the OS, as well as differences between .Net and mono, which you'll have to workaround. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
On 09/05/2015 13:00, mono-list-requ...@lists.ximian.com wrote:
Thanks for your answer.
You probably right for the hellogtk.cs program but what about the Winforms
one ?
Here is the code of hellowinforms.cs:
using System;
using System.Windows.Forms;
public class HelloWorld : Form
{
static public void Main ()
{
Application.Run (new HelloWorld ());
}
public HelloWorld ()
{
Text = "Hello Mono World";
}
}
initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException:
/Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib
Hi,
Are you on Snow Leopard (OSX 10.6) by any chance ? I've noticed its gone from
the supported OS list
but the removal of support is not mentioned in the Release Notes.
When I tried to run my application which uses a bitmap on Snow Leopard I got
the same error...
Unhandled Exception:
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException:
/Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib
at (wrapper managed-to-native) System.Drawing.GDIPlus:GdiplusStartup
(ulong&,System.Drawing.GdiplusStartupInput&,System.Drawing.GdiplusStartupOutput&)
at System.Drawing.GDIPlus..cctor () [0x0] in :0
--- End of inner exception stack trace ---
at System.Drawing.Bitmap..ctor (Int32 width, Int32 height, PixelFormat format)
[0x0] in :0
I then ran with MONO_LOG_LEVEL=debug and got
Mono: DllImport attempting to load:
'/Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib'.
Mono: DllImport error loading library
'/Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib':
'dlopen(/Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib,
9): Symbol not found: __tlv_bootstrap
Referenced from:
/Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libpixman-1.0.dylib
Expected in: /usr/lib/libSystem.B.dylib
It appears its been compiled to be compatible with 10.7 minimum which is where
__tlv_bootstrap appeared,
which funny as its still a 32 bit framework but doesn't support any 32 bit
version of OSX.
If you are not on Snow Leopard then I suggest running it with
MONO_LOG_LEVEL=debug and seeing what that throws out.
Dave
___
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
Hi Edward, Thank you first for your detailed answer. You wrote: "So the big questions are - What do you want to accomplish? Are you planning to develop mono sources and contribute to mono? Or do you just want to learn mono and start doing cross-platform stuff like you were doing on .Net with VS?" Actually I simply want to make run on a Mac a WCF Service Windows Forms client application I just developed with VS on Windows. The WCF (duplex) service is hosted on iis and the clients normally run on Windows but I have some Mac workstations on which I would need to be able to run the WCF client. I thought this was possible with mono and just wanted to try that. I do not intend to develop nor compile my app on the Mac/mono. I just want to deploy and run the already compiled WCF Winforms client .exe app with its WCF config file to consume the WCF service. Thank you to let me know if there is any chance to succeed and how. Actually, when a tried to run my client on mono I got the same error message than I got when I tried to run the little hello Winforms test app: Unable to find some dynamic linked library of the mono framework. But these files appear to be correctly installed... Thanks again. Pierre-François aka Chip Envoyé de mon iPhone Pierre-Francois. > Le 10 mai 2015 à 16:40, Edward Ned Harvey (mono) > a écrit : > > So the big questions are - What do you want to accomplish? Are you planning > to develop mono sources and contribute to mono? Or do you just want to learn > mono and start doing cross-platform stuff like you were doing on .Net with VS? ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
> From: mono-list-boun...@lists.ximian.com [mailto:mono-list- > boun...@lists.ximian.com] On Behalf Of ChipRaptor > > I compiled and ran the basic tests proposed on the mono page at > http://www.mono-project.com/docs/getting-started/mono-basics/ I recommend, forget about it unless you care - GTK isn't usually used anywhere except on Linux. Normally on the mac, you're using Xamarin.Mac, or MonoMac. Normally on windows, you're using WinForms or WPF. Definitely *don't* bother with winforms on non-windows platforms. Nobody has ever had a good experience with that. If you're looking for a cross-platform GUI toolkit, you can look at Eto.Forms and XSP. But I think most people just design business logic separate from GUI code, and build native GUI's on Xam.Mac, GTK#, and Winforms/WPF. If you're looking for cross-platform GUI toolkit for mobile devices, there's Xamarin.Forms... And probably some competitors, but I don't do this, so I don't know. So the big questions are - What do you want to accomplish? Are you planning to develop mono sources and contribute to mono? Or do you just want to learn mono and start doing cross-platform stuff like you were doing on .Net with VS? If you want to just develop .Net applications, I would suggest: Install MonoDevelop (which is completely free, and confusing, because after installation its name will be "Xamarin Studio," but if you were to go to the xamarin downloads page to download xamarin studio, it's not free). Play around with the Xamarin.Mac Hello Mac. Play around with GTK# on linux. Installing the MDK is pretty brainless and straightforward. And in fact, you can run your apps just because the MDK is installed. But you don't want to (and sometimes can't) make it a requirement for end users to install MDK in order to run your app - If you pay for Xam.Mac, there is a checkbox inside your xam.mac project to bundle the runtime with your app. This is by far, the recommended way to go. (And a requirement, in order to distribute in the appstore). MonoMac and Xamarin.Mac are the same thing - except Xam.Mac has been developed more with more features added onto it. So you can get a good idea how to design basic forms and how the threading model works using MonoMac, and then pay for Xam.Mac when or if you need it. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] just installed mono, most basic test failed.
Thanks for your answer.
You probably right for the hellogtk.cs program but what about the Winforms
one ?
Here is the code of hellowinforms.cs:
using System;
using System.Windows.Forms;
public class HelloWorld : Form
{
static public void Main ()
{
Application.Run (new HelloWorld ());
}
public HelloWorld ()
{
Text = "Hello Mono World";
}
}
And here are the compilation and launching lines and the resulting errors:
imac-de-claire-lise-culand-4:Documents PF$ mcs hellowinforms.cs -pkg:dotnet
imac-de-claire-lise-culand-4:Documents PF$ mono hellowinforms.exe
Unhandled Exception:
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Windows.Forms.WindowsFormsSynchronizationContext --->
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Windows.Forms.ThemeEngine --->
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Windows.Forms.ThemeWin32Classic --->
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Drawing.KnownColors --->
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException:
/Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib
at (wrapper managed-to-native) System.Drawing.GDIPlus:GdiplusStartup
(ulong&,System.Drawing.GdiplusStartupInput&,System.Drawing.GdiplusStartupOutput&)
at System.Drawing.GDIPlus..cctor () [0x0] in :0
--- End of inner exception stack trace ---
at System.Drawing.KnownColors..cctor () [0x0] in :0
--- End of inner exception stack trace ---
at System.Drawing.Color.get_Black () [0x0] in :0
at System.Windows.Forms.ThemeWin32Classic..cctor () [0x0] in :0
--- End of inner exception stack trace ---
at System.Windows.Forms.ThemeEngine..cctor () [0x0] in :0
--- End of inner exception stack trace ---
at System.Windows.Forms.SystemInformation.get_MenuAccessKeysUnderlined ()
[0x0] in :0
at System.Windows.Forms.Control..ctor () [0x0] in :0
at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:.ctor
()
at System.Windows.Forms.WindowsFormsSynchronizationContext..cctor ()
[0x0] in :0
--- End of inner exception stack trace ---
at System.Windows.Forms.Control..ctor () [0x0] in :0
at System.Windows.Forms.ScrollableControl..ctor () [0x0] in :0
at System.Windows.Forms.ContainerControl..ctor () [0x0] in :0
at System.Windows.Forms.Form..ctor () [0x0] in :0
at HelloWorld..ctor () [0x0] in :0
at (wrapper remoting-invoke-with-check) HelloWorld:.ctor ()
at HelloWorld.Main () [0x0] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An
exception was thrown by the type initializer for
System.Windows.Forms.WindowsFormsSynchronizationContext --->
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Windows.Forms.ThemeEngine --->
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Windows.Forms.ThemeWin32Classic --->
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Drawing.KnownColors --->
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException:
/Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib
at (wrapper managed-to-native) System.Drawing.GDIPlus:GdiplusStartup
(ulong&,System.Drawing.GdiplusStartupInput&,System.Drawing.GdiplusStartupOutput&)
at System.Drawing.GDIPlus..cctor () [0x0] in :0
--- End of inner exception stack trace ---
at System.Drawing.KnownColors..cctor () [0x0] in :0
--- End of inner exception stack trace ---
at System.Drawing.Color.get_Black () [0x0] in :0
at System.Windows.Forms.ThemeWin32Classic..cctor () [0x0] in :0
--- End of inner exception stack trace ---
at System.Windows.Forms.ThemeEngine..cctor () [0x0] in :0
--- End of inner exception stack trace ---
at System.Windows.Forms.SystemInformation.get_MenuAccessKeysUnderlined ()
[0x0] in :0
at System.Windows.Forms.Control..ctor () [0x0] in :0
at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:.ctor
()
at System.Windows.Forms.WindowsFormsSynchronizationContext..cctor ()
[0x0] in :0
--- End of inner exception stack trace ---
at System.Windows.Forms.Control..ctor () [0x0] in :0
at System.Windows.Forms.ScrollableControl..ctor () [0x0] in :0
at System.Windows.Forms.ContainerControl..ctor () [0x0] in :0
at System.Windows.Forms.Form..ctor () [0x0] in :0
at HelloWorld..ctor () [0x0] in :0
at (wrapper remoting-invoke-with-check) HelloWorld:.ctor ()
at HelloWorld.Main () [0x0] in :0
imac-de-claire-lise-culand-4:Documents PF$
Again the error messages seems to say the
/Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib is
missing.
But it exists in the give
Re: [Mono-list] just installed mono, most basic test failed.
Hi It seems like You have forgotten/missed to install GTK# http://www.mono-project.com/docs/gui/gtksharp/beginners-guide/#getting-set-up You can compile it from source: https://github.com/mono/gtk-sharp If You install Xamarin.Studo (Monodevelop based IDE) everything shoudl be installed automagically. regards Mel On 20150509 07:35 , ChipRaptor wrote: Hi everyone, sorry for this mono newbie question: I just installed mono (4.0.0) on an iMac running Mac OS X 10.6.8. I'm a .Net developper but I am completely new to mono... I compiled and ran the basic tests proposed on the mono page at http://www.mono-project.com/docs/getting-started/mono-basics/ But the first one only was succesfull... (Test.exe which actually is the first Hello world program, correctly displaying "Hello Mono World".) But all the other proposed test display a lot of error messages. See hereafter the terminal full terminal output: imac-de-claire-lise-culand-4:Documents PF$ mono test.exe Hello Mono World imac-de-claire-lise-culand-4:Documents PF$ mono hellogtk Cannot open assembly 'hellogtk': No such file or directory. imac-de-claire-lise-culand-4:Documents PF$ mono hellogtk.exe Unhandled Exception: System.DllNotFoundException: /Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgtk-quartz-2.0.0.dylib at (wrapper managed-to-native) Gtk.Application:gtk_init (int&,intptr&) at Gtk.Application.Init () [0x0] in :0 at Hello.Main () [0x0] in :0 [ERROR] FATAL UNHANDLED EXCEPTION: System.DllNotFoundException: /Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgtk-quartz-2.0.0.dylib at (wrapper managed-to-native) Gtk.Application:gtk_init (int&,intptr&) at Gtk.Application.Init () [0x0] in :0 at Hello.Main () [0x0] in :0 imac-de-claire-lise-culand-4:Documents PF$ mono hello.exe Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.WindowsFormsSynchronizationContext ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.ThemeEngine ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.ThemeWin32Classic ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.KnownColors ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException: /Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib at (wrapper managed-to-native) System.Drawing.GDIPlus:GdiplusStartup (ulong&,System.Drawing.GdiplusStartupInput&,System.Drawing.GdiplusStartupOutput&) at System.Drawing.GDIPlus..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Drawing.KnownColors..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Drawing.Color.get_Black () [0x0] in :0 at System.Windows.Forms.ThemeWin32Classic..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Windows.Forms.ThemeEngine..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Windows.Forms.SystemInformation.get_MenuAccessKeysUnderlined () [0x0] in :0 at System.Windows.Forms.Control..ctor () [0x0] in :0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:.ctor () at System.Windows.Forms.WindowsFormsSynchronizationContext..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Windows.Forms.Control..ctor () [0x0] in :0 at System.Windows.Forms.ScrollableControl..ctor () [0x0] in :0 at System.Windows.Forms.ContainerControl..ctor () [0x0] in :0 at System.Windows.Forms.Form..ctor () [0x0] in :0 at HelloWorld..ctor () [0x0] in :0 at (wrapper remoting-invoke-with-check) HelloWorld:.ctor () at HelloWorld.Main () [0x0] in :0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.WindowsFormsSynchronizationContext ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.ThemeEngine ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.ThemeWin32Classic ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.KnownColors ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException: /Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib at (wrapper managed-to-native) System.Drawing.GDIPlus:GdiplusStartup (ulong&,System.Drawing.GdiplusStartupInput&,System.Drawing.GdiplusStartupOutput&) at System.Drawing.GDIPlus..cctor () [0x0] in :0 --- End
[Mono-list] just installed mono, most basic test failed.
Hi everyone, sorry for this mono newbie question: I just installed mono (4.0.0) on an iMac running Mac OS X 10.6.8. I'm a .Net developper but I am completely new to mono... I compiled and ran the basic tests proposed on the mono page at http://www.mono-project.com/docs/getting-started/mono-basics/ But the first one only was succesfull... (Test.exe which actually is the first Hello world program, correctly displaying "Hello Mono World".) But all the other proposed test display a lot of error messages. See hereafter the terminal full terminal output: imac-de-claire-lise-culand-4:Documents PF$ mono test.exe Hello Mono World imac-de-claire-lise-culand-4:Documents PF$ mono hellogtk Cannot open assembly 'hellogtk': No such file or directory. imac-de-claire-lise-culand-4:Documents PF$ mono hellogtk.exe Unhandled Exception: System.DllNotFoundException: /Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgtk-quartz-2.0.0.dylib at (wrapper managed-to-native) Gtk.Application:gtk_init (int&,intptr&) at Gtk.Application.Init () [0x0] in :0 at Hello.Main () [0x0] in :0 [ERROR] FATAL UNHANDLED EXCEPTION: System.DllNotFoundException: /Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgtk-quartz-2.0.0.dylib at (wrapper managed-to-native) Gtk.Application:gtk_init (int&,intptr&) at Gtk.Application.Init () [0x0] in :0 at Hello.Main () [0x0] in :0 imac-de-claire-lise-culand-4:Documents PF$ mono hello.exe Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.WindowsFormsSynchronizationContext ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.ThemeEngine ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.ThemeWin32Classic ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.KnownColors ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException: /Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib at (wrapper managed-to-native) System.Drawing.GDIPlus:GdiplusStartup (ulong&,System.Drawing.GdiplusStartupInput&,System.Drawing.GdiplusStartupOutput&) at System.Drawing.GDIPlus..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Drawing.KnownColors..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Drawing.Color.get_Black () [0x0] in :0 at System.Windows.Forms.ThemeWin32Classic..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Windows.Forms.ThemeEngine..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Windows.Forms.SystemInformation.get_MenuAccessKeysUnderlined () [0x0] in :0 at System.Windows.Forms.Control..ctor () [0x0] in :0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:.ctor () at System.Windows.Forms.WindowsFormsSynchronizationContext..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Windows.Forms.Control..ctor () [0x0] in :0 at System.Windows.Forms.ScrollableControl..ctor () [0x0] in :0 at System.Windows.Forms.ContainerControl..ctor () [0x0] in :0 at System.Windows.Forms.Form..ctor () [0x0] in :0 at HelloWorld..ctor () [0x0] in :0 at (wrapper remoting-invoke-with-check) HelloWorld:.ctor () at HelloWorld.Main () [0x0] in :0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.WindowsFormsSynchronizationContext ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.ThemeEngine ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.ThemeWin32Classic ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.KnownColors ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException: /Library/Frameworks/Mono.framework/Versions/4.0.0/lib/libgdiplus.dylib at (wrapper managed-to-native) System.Drawing.GDIPlus:GdiplusStartup (ulong&,System.Drawing.GdiplusStartupInput&,System.Drawing.GdiplusStartupOutput&) at System.Drawing.GDIPlus..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Drawing.KnownColors..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Drawing.Color.get_Black () [0x0] in :0 at System.Windows.Forms.ThemeWin32Classic..cctor () [0x0] in :0 --- End of inner exception stack trace --- at System.Windows.Forms.ThemeEngine..cctor () [0x0] in :0
