[Mono-winforms-list] Can't even get MonoHelloWorld to run. What am I doing wrong?

Jonathan Pobst monkey at jpobst.com
Tue Feb 12 10:26:24 EST 2008


Try redirecting the error output to a file, and see if it produces anything:

mono MonoHelloWorld.exe 2> error.log

I think the stuff you pasted is normal if you run using verbose.

Jonathan


Richard.Foster at quixotecorp.com wrote:
> Hi there,
> 
> I have occasionally been poking at the Winforms support to see how far
> it's got, but always hit a roadblock. Having tried a few things, I have
> now come to the conclustion that it is something related to my
> environment which is causing the trouble. Even the "MonoHelloWorld" code
> (from
> http://anonsvn.mono-project.com/viewcvs/trunk/winforms/hello/swf-hello.c
> s?rev=44917&view=markup) won't run under Mono (1.2.6 or 1.9) if built
> using Visual Studio 2005.
> 
> Using the latest 1.9 test release (installed using the installer) I get
> the following response (when running verbose):
> 
> D:\Data\ ... \bin\Debug>mono -v MonoHelloWorld.exe
> 
> Method (wrapper runtime-invoke) System.Object:runtime_invoke_void_string
> (object,intptr,intptr,intptr) emitted at 00F50028 to 00F500BD (code
> length 149) [MonoHelloWorld.exe]
> Method System.OutOfMemoryException:.ctor (string) emitted at 00F500C0 to
> 00F500E3 (code length 35) [MonoHelloWorld.exe]
> Method System.SystemException:.ctor (string) emitted at 00F50100 to
> 00F50123 (code length 35) [MonoHelloWorld.exe]
> Method System.Exception:.ctor (string) emitted at 00F50130 to 00F50148
> (code length 24) [MonoHelloWorld.exe]
> Method System.Exception:set_HResult (int) emitted at 00F50148 to
> 00F50156 (codelength 14) [MonoHelloWorld.exe]
> Method System.NullReferenceException:.ctor (string) emitted at 00F50158
> to 00F5017E (code length 38) [MonoHelloWorld.exe]
> Method System.StackOverflowException:.ctor (string) emitted at 00F50180
> to 00F50196 (code length 22) [MonoHelloWorld.exe]
> 
> When attempting to run without the -v option, there is no visible
> result.
> 
> Running the executable directly (i.e. using the .NET 2.0 framework), it
> works perfectly (as far as I can judge).
> 
> Since there is no reverence to this the FAQ etc, this obviously isn't
> the sort of thing everyone runs into... so can anyone suggest what I
> might be doing wrong?
> 
> Regards,
> Richard
> _______________________________________________
> Mono-winforms-list maillist  -  Mono-winforms-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list
> 
> 



More information about the Mono-winforms-list mailing list