[Mono-dev] Human Japanese 2.0 .NET2.0 fails

John Moser john.r.moser at gmail.com
Thu Feb 23 00:16:33 UTC 2012


lextm <support <at> lextm.com> writes:

> 
> Sorry for my quick fingers. I should have went through your entire message.

No, I should have noted at the top that I tested on both Mono and .NET 2.0, and 
that I had included the dump of both and copied both lists as I felt the output 
would help both.  You have to get like 80% down the message before it makes any 
sense why I sent this to the Mono group at all, which is stupid.

In the future I will introduce my messages more clearly.

> 
> You posted in fact two scenarios,
> 
> 1. .NET 2 issue on Wine
> Like I said this has nothing to do with Mono and of course you have posted
> to Wine guys. They should look into it to see what is the cause.
> 

Correct.  I felt the debugging data may be useful to determine what .NET is 
trying to do and thus why it doesn't work in Mono.  (I know nothing about Mono 
architecturally or as a project)

> 2. Mono issue on Windows XP and Wine
> 
> Like the two articles indicate, System.Management is out of Mono's scope and
> even on Windows this namespace is not supported,
> 
> http://www.mono-project.com/Mono_Project_Roadmap
> 
> http://www.mono-project.com/Compatibility
> 
> Therefore, if you want to stick to Microsoft .NET and Wine, you need to wait
> till Wine guys find out the root cause and fix it.
> 

Right.  Ok.

> If you want to use Mono, personally I strongly recommend you switch to
> native Mono on Linux, and use LDAP directly instead of System.Management if
> possible,
> 
> http://www.mono-project.com/FAQ:_General
> 

This isn't my project, I don't know what it's doing all that for.  I'll contact 
the people who make it.

> Of course, migrating to native Mono means you need to rewrite your current
> code which depends on System.Management.
> 
> Regards,
> Lex
> 




More information about the Mono-devel-list mailing list