The corefx repo contains the library implementation (called "CoreFX") for .NET Core. It includes System.Collections, System.IO, System.Xml, and many other components. You can see more information in Documentation. The corresponding .NET Core Runtime repo contains the runtime implementation (called "CoreCLR") for .NET Core. It includes RyuJIT, the .NET GC, and many other components. Runtime-specific library code - namely System.Private.Corelib - lives in the CoreCLR repo. It needs to be built and versioned in tandem with the runtime. The rest of CoreFX is agnostic of runtime-implementation and can be run on any compatible .NET runtime.
.NET Core now has a source index: https://source.dot.net
| Inner x64 Debug | Inner x64 Release | Outer x64 Debug | Outer x64 Release | |
|---|---|---|---|---|
| CentOS 7.1 | ||||
| Debian 8 | ||||
| Fedora 23 | ||||
| Fedora 24 | ||||
| openSUSE 42.1 | ||||
| OS X 10.11 | ||||
| Red Hat 7.2 | ||||
| Ubuntu 14.04 | ||||
| Ubuntu 16.04 | ||||
| Ubuntu 16.10 | ||||
| PortableLinux | ||||
| Windows 7 | ||||
| Windows 8.1 | ||||
| Windows 10 | ||||
| Windows Nano Server 2016 | ||||
| Code Coverage (Windows) |
Some of the best ways to contribute are to try things out, file bugs, and join in design conversations. If you are having issues with the Full .NET Framework or .NET Runtime, the best way to file a bug is at Connect or through Product Support if you have a contract.
Want to get more familiar with what's going on in the code?
Looking for something to work on? The list of up-for-grabs issues is a great place to start. See some of our guides for more details:
We've also started to share some of our direction via more higher-level documentation, specifically:
You are also encouraged to start a discussion by filing an issue or creating a gist.
You can discuss .NET OSS more generally in the .NET Foundation forums.
Want to chat with other members of the CoreFX community?
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information, see the .NET Foundation Code of Conduct.
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) [email protected]. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
The repo contains the source for each of the assemblies that comprises .NET Core. Each Microsoft.* or System.* folder under
src represents an individual library. Each such folder may contain a ref folder,
which contains the source representing the "contract" or "reference assembly" for that library. It may also contain a src folder,
which contains the source for some or all of the implementation for that library (some implementation may live in System.Private.Corelib in the
coreclr repo, with the build tooling generating type forwards from the library assembly to System.Private.Corelib.)
It may also contain a test folder containing the tests associated with that library, whether the implementation source lives in corefx
or in coreclr.
Daily builds of .NET Core components are published to dotnet-core MyGet gallery. The latest version number of each library can be seen in that gallery.
.NET Core (including the corefx repo) is licensed under the MIT license.
.NET Core is a .NET Foundation project.
There are many .NET related projects on GitHub.
- The .NET home repo links to 100s of .NET projects, from Microsoft and the community.
- The .NET Core repo links to .NET Core related projects from Microsoft.
- The ASP.NET home repo is the best place to start learning about ASP.NET Core.
- dotnet.github.io is a good place to discover .NET Foundation projects.