[Mono-devel-list] Compiling class libraries using VS.NET

[A Rafael D Teixeira]

Well, each subdirectory inside mcs/class is to be compiled separately to a 
different assembly (so it is a separate csproj inside your sln file), the 
duplication occurs as internal classes (blackboxed inside the assemblies). 
Specifically those are classes to access methods in the runtime environment 
(P/Invoke).

We can't refactor without breaking the full compatibility with MS versions.

Hope it helps understanding it,

Rafael Teixeira
Brazilian Polymath
Mono Hacker since 16 Jul 2001
English Blog: http://monoblog.blogspot.com/
Brazilian Portuguese Blog: http://monoblog.weblogger.terra.com.br/



>From: "Richard Thombs" <mono at stony.org>
>To: <mono-devel-list at lists.ximian.com>
>Subject: [Mono-devel-list] Compiling class libraries using VS.NET
>Date: Thu, 16 Oct 2003 21:45:45 -0700
>
>Hi,
>
>To make it easier for me to browse and trace through the Mono source, I
>wrote a tool that creates a VS.NET project from all of the files in
>mcs/class. While trying to get the resulting project to compile, I
>noticed that there were a few duplicate class definitions that I
>couldn't explain. Most of them have to do with a definition existing in
>corelib as well as in some other location.
>
>For example: System.IO.MonoIO is declared both in
>class\System\System.IO\MonoIO.cs and class\corlib\System.IO\MonoIO.cs
>
>I was wondering what the purpose of this duplication is and if there are
>any hard and fast rules about which I should include and which I should
>ignore?
>
>Thanks,
>
>Richard.
>
>_______________________________________________
>Mono-devel-list mailing list
>Mono-devel-list at lists.ximian.com
>http://lists.ximian.com/mailman/listinfo/mono-devel-list

_________________________________________________________________
MSN Messenger: instale grátis e converse com seus amigos. 
http://messenger.msn.com.br