Completed (26 days)
Open .NET & CoreCLR
Completed (47 days)
Completed (19 days)
Completed (14 days)
Security implications of open CoreCLR (CoreRun.exe)
Completed on 05-Feb-2016 (26 days) -- Updated on 23-Nov-2016
Some of the conclusions of this project aren't applicable anymore.
To know more about all this, read "OVER-8-MONTH-LATER UPDATE" in the Open .NET & CoreCLR section.
As far as Project 7 already includes my impressions about open .NET and my first participation there, visiting that project is precisely the best way to get some Preliminary ideas. More specifically, the following (Introduction) sections:
In summary, this project will be dealing with CoreCLR by focusing on compilation aspects and closely-related issues (e.g., CoreRun.exe and its impact on security), rather than on specific pieces of code (what Project 7 is precisely about).
As explained in the also-updated Project 7, Microsoft has modified the way in which .NET programs can communicate with the CoreCLR libraries (and with the ones in other repositories, like CoreFX). This fact has a big impact on the current project, as far as its whole purpose was precisely analysing what is now an obsolete proceeding. Nevertheless and except for this clarification, I will keep it as originally written because of describing one of the preliminary steps within the evolution of a complex framework.
The most relevant ideas can be summarised in the following points: