Skip to content

Instantly share code, notes, and snippets.

@lucasmeijer
lucasmeijer / gist:9de952d508cd9b737518
Last active April 6, 2016 14:27
What is up and down in CoreFX, CoreCLR world.
I've been trying to understand how all moving parts of CoreFX, CoreCLR & ReferenceSource, especially related to
mscorlib. These are my notes / conclusions. If you have more information, or see something that is wrong, please
let me know!
the CoreCLR repo, has an embedded mscorlib inside of it. When diffing this against the referencesource mscorlib,
it looks like it forked at some point, and has received some minor cleanups. most occuring changes:
- change license header
- remove [ResourceExposure] and [ResourceConsumption] attributes.
- some modest improvements. (files like Task.cs, Thread.cs, AppDomain.cs, are files with relatively high amount of changes)
- cleanup. if referencesource code had #if DOTNETCORE, that define has been removed in the coreclr one, as it is now always true.