Ok ... I think I got it. Stupid me + f#$!& windows = bad combo.
I think I screwed it all up by defining mono_jit_init_version ("MooseQT Root
Domain","v1.1.4322").
Windows (at least windows 7) screwed it totally by suppressing all error
messages.
Now on my virtual win xp the error message was more explicit something like
"Missing method System.CodeDom.Compiler.CodeDomProvider::CreateProvider ".
Frank
Am 02.08.2010 um 15:44 schrieb Frank Fuchs:
> Hi,
> yes the .bat file works standalone. I don't know how to find out whether or
> not it is invoked.
>
> Frank
>
>> On 02.08.2010 12:13, Frank Fuchs wrote:
>> > No this does not seem to be the cause. Any further suggestions? I will try
>> > to assemble a test case.
>> > May be it's related to this thing here (
>> > http://unity3d.com/unity/whats-new/unity-2.6 ... they mention a failing
>> > CreateProvider)
>>
>> Did you check whether the BAT file was invoked or whether the
>> BAT file is working standalone?
>>
>> Robert
>
_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/mono-devel-list
