[Mono-dev] Microsoft .NET and Mono integration - GSOC 2017

Ludovic Henry luhenry at microsoft.com
Thu Mar 23 14:20:55 UTC 2017

Hi Michael,

Thank you for your interest in these projects! :)

To answer your questions:

1. Yes, passing tests would be the first goal, and even if some of these tests are 12 years old, they are still very relevant today.

2. Corefx only support a subset of the platforms we support (corefx supports windows, linux, OSX, freebsd and netbsd). So adding support for the different platforms supported by Mono (Android, iOS, Haiku, etc.) means that we need to ensure that the corefx code works just as well on these new platforms, than it does on the platforms that it already supports. As it already support the 3 main platforms (Windows, Linux and BSD - for OSX, FreeBSD and NetBSD), porting it to support the other platforms wouldn't entail a lot of changes, as it would mostly be adaptations to platform-specific behaviours and bugs.

If you have any more questions, please feel free to ask.

Thank you very much,


On 19 Mar 2017, at 10:37, Michael Viveros <michaelviveros at gmail.com<mailto:michaelviveros at gmail.com>> wrote:


I’m Michael Viveros and I’m interested in Mono’s GSOC projects<http://www.mono-project.com/community/google-summer-of-code/projects/#microsoft-net-and-mono-integration> related to Microsoft .NET and Mono integration (mentor Ludovic Henry):
Import ThreadPool from CoreRT
Import System.IO.FileStream from CoreFX
Import Process from CoreFX

I have some questions about the project, some of which are follow-up questions to this thread from Wed. March 15th:

1. Would 1 goal of these projects be getting the tests to pass?
For example, getting the tests to pass in https://github.com/mono/mono/tree/master/mcs/class/corlib/Test/System.IO for the System.IO.FileStream project.
Some of the tests there are over 12 years old so I’m not sure if they’re still relevant.

2. What would adding support to CoreFX for different platforms supported by Mono (Android, iOS, Haiku, etc.) entail?
I briefly looked over the mono code for w32file-unix.c<https://github.com/mono/mono/blob/8b671a8c31368e2046aa9546c46f01b99c5c8008/mono/metadata/w32file-unix.c> and it looked quite massive, porting it over to CoreFX seems like it could be a lot of work.

Mono-devel-list mailing list
Mono-devel-list at lists.dot.net<mailto:Mono-devel-list at lists.dot.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dot.net/pipermail/mono-devel-list/attachments/20170323/2928486e/attachment.html>

More information about the Mono-devel-list mailing list