[Mono-list] difference between Mono et Microsoft.Net

[Jonathan Pryor]

On Sat, 2010-01-09 at 21:13 -0800, Vu Duy Truong wrote:
> Hello I am a student. And I study Mono and Microsoft.Net. In my study,
> I found that there are differences between Mono and Microsoft.Net.

This is to be expected.  .NET is huge, and Mono hasn't had time to
reimplement everything.  For example, Mono has no WPF implementation,
and Mono's WCF implementation is primarily targeting the Silverlight
profile (which differs from the desktop .NET profile).

Mono has implemented large fractions of .NET, but not all of it.

>  For example, in Mono, there is not some libraries as
> System.Configuration.Internal

Uh, you mean *these* types?

        http://anonsvn.mono-project.com/source/trunk/mcs/class/System.Configuration/System.Configuration.Internal/

Those are in the System.Configuration.dll assembly, and Mono has them.
(Why you'd use types explicitly documented as "for internal use only" is
another matter.)

>  or System.Configuration.Provider.

Again, Mono *does* have these types: 

        http://anonsvn.mono-project.com/source/trunk/mcs/class/System.Configuration/System.Configuration.Provider/

They're also in System.Configuration.dll.  Furthermore, Mono has had
these types since (at least!) Mono 1.1.10 (November 11, 2005).

> Moreover, in Mono, the library is like Microsoft.Net, there is no
> method as in Microsoft.Net. Can you give me reasons for these
> differences. Thank you. 

I don't understand this comment.

 - Jon