[Mono-dev] CoreFX/CoreCLR dependencies

Miguel de Icaza miguel at microsoft.com
Mon Oct 17 19:09:33 UTC 2016

Hello Marek,

I do not think that we need to migrate our test suite at all.

We can just add xUnit as a source of tests that Mono runs, in addition to the existing NUnit tests that we have.

From: Mono-devel-list <mono-devel-list-bounces at lists.dot.net> on behalf of Marek Safar <marek.safar at gmail.com>
Date: Thursday, October 6, 2016 at 11:59 AM
To: "mono-devel-list at lists.dot.net" <mono-devel-list at lists.dot.net>
Subject: [Mono-dev] CoreFX/CoreCLR dependencies


I'd like to share some plans we have for integration of more dotnet code. In 2014 we started replacing large chunks of Mono code with referencesource sources. This process has been going quite well and it has improved .NET compatibility and Mono quality significantly.

Referencesource is read-only copy of the .NET framework sources which have very high backward compatibility requirements, for historical reasons Windows specific and does not operate in open source mode. [https://github.com/Microsoft/referencesource<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Freferencesource&data=01%7C01%7Cmiguel%40microsoft.com%7C7dd7799d76d64ea741c408d3ee01c833%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=nhCqgW1D5dx4S98daznXyZ0RRiyORjIB19FSr1Dxc7w%3D&reserved=0>]

CoreFX/CoreCLR are true open source projects with performance improvements, multi-platform support, legacy code cleaned up, unit tests. [https://github.com/dotnet/corefx<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fcorefx&data=01%7C01%7Cmiguel%40microsoft.com%7C7dd7799d76d64ea741c408d3ee01c833%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=BscK5DQpcLFzzBKpgs60IYOkg2Q%2FLRBhWkSOcJaBfzc%3D&reserved=0>]

We’d like to take benefits of that code and where appropriate (think of compatibility) take source code from CoreFX/CoreRT [1] repositories. CoreFX uses xUnit framework and Mono is using NUnit-like frameworks which means we’ll have to migrate before any tests can be used as maintaining two different test frameworks does not appear to me as good solution.

As both are open source project I’d like to see Mono changes (when needed) to go into these repos and only when not possible have our forks at https://github.com/mono/corefx<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmono%2Fcorefx&data=01%7C01%7Cmiguel%40microsoft.com%7C7dd7799d76d64ea741c408d3ee01c833%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=KLf3ZAdG4U%2FASKKPp1HPYgVRsn8Q%2FEpfnvjiWzKcwZQ%3D&reserved=0> and https://github.com/mono/corert<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmono%2Fcorert&data=01%7C01%7Cmiguel%40microsoft.com%7C7dd7799d76d64ea741c408d3ee01c833%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=XoQFYMbn1uV3ky0cbRDQMXy8ngFTOvGVuJk5LM7JyM4%3D&reserved=0> used. I don’t know yet what cadency we’ll use to update these forks as it mostly depends on what code we’ll end up using.

- Marek

[1] Why CoreRT and not CoreCLR? We are interested in mscorlib code only and this repo is much smaller to submodule. There is some talk to have mscorlib specific repo in the future but that’s not available yet.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dot.net/pipermail/mono-devel-list/attachments/20161017/0e656770/attachment-0001.html>

More information about the Mono-devel-list mailing list