[Mono-dev] Problems with mono continuation

[Rafael Teixeira]

You have to start with the mono runtime, like a command line like:

mono yourapp.exe

That is what you always have to do in other OSes (normally having script
files to hide it from the end user), and the only way in windows to run a
managed application with Mono instead of .NET.

As Robert already said, your app isn't compatible with .NET, as it uses a
Mono specific lib that depends on Mono's runtime support for continuations,
exposed through that InternalCall.

Hope it makes things clearer,

Rafael "Monoman" Teixeira
---------------------------------------
"To be creative means to be in love with life. You can be creative only if
you love life enough that you want to enhance its beauty, you want to bring
a little more music to it, a little more poetry to it, a little more dance
to it."
Osho


On Thu, Feb 25, 2010 at 9:43 AM, raccoon <timo.heubach at gmail.com> wrote:

>
> Hi,
>
> Thought about that too... I tried copying all System.dll, Mono.Tasklets.dll
> and mscorlib.dll to the executable folder and still the same error. The odd
> thing is that I can attach VS to the process with managed code debugging
> and
> I see the GAC version of the mscorlib.dll as loaded... Why doesn't it load
> the assembly in the executable folder but instead uses the global assembly
> cache version? But doesn't this mean that all Mono application run under
> windows use the .NET CLR?
>
> -Timo
> --
> View this message in context:
> http://n4.nabble.com/Problems-with-mono-continuation-tp1568629p1568945.html
> Sent from the Mono - Dev mailing list archive at Nabble.com.
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20100225/8c7809fe/attachment.html